YOUR MESSAGE. YOUR CONTROL.

A safer space to ask.

Every message is checked before it reaches an AI provider. Review masked content before sharing it.

Chat access key

This key grants chat access only. Administrators already signed in to the management console can open chat directly.

Restoring your secure session…

INSPECT → REVIEW → SEND

Ask with confidence.

Sensitive personal and financial data is masked. Hard-block policies remain enforced.

● Pre-send protectionAI provider

◇

Your prompt passes through a security check first.

Choose a configured provider, then write a message. Changing providers starts a new conversation. Nothing goes to the AI while you type or review a warning.

Waiting for the provider…

Your message

Write a message to check it.

Check automatically

Drafts are inspected after a short typing pause. The server checks again before every send.

You approve masking

Personal and financial matches show a masked preview. Only that exact preview can be confirmed.

Only approved text leaves

API keys, private keys, passwords, and custom Block rules stop the request. Confirmation cannot override them.

Text-only conversations

Up to 10 turns per conversation. History stays in this tab's memory and clears on reload or sign-out. Provider retention policies still apply to sent text. Detectors are pattern-based and may miss sensitive data.

REVIEW BEFORE SHARING

Sensitive information detected

Only the masked conversation below will be sent to the selected AI provider.

Exact conversation to send

The preview expires after 5 minutes. Changing a draft, provider, or policy requires a new check.

CONNECT YOUR AI APP

One gateway. Your choice of client.

MCP connects an AI app to your tools. To check every chat message before model access, use Secure Chat on this page with an administrator-configured AI provider.

What this connection protects

AI app → MCP tool request → gateway checks → assigned destination server.

Messages sent directly to another AI website do not pass through this gateway. Secure Chat currently supports text conversations without MCP tool execution.

Choose your app

Gateway MCP server URL

Configuration example · placeholders only

Official setup documentation ↗

Before connecting

Ask an administrator to create an individual MCP client key and assign a destination server.
Use that client key for MCP authentication. Admin keys and Chat access keys grant different access.
The destination must implement MCP initialization and tool discovery. An AI model API URL is not an MCP destination.
This gateway forwards POST requests, including streamed responses. Separate GET event channels, DELETE session termination, and OAuth discovery are not implemented.
After connecting, list tools in the client, run a harmless tool, and ask an administrator to verify its Audit log event. This guide does not run a connection test.

App features depend on account, region, workspace policy, and client version. Setup guidance checked against official documentation on 10 November 2026.

Single Worker · Server-enforced checks · No prompt or reply storage in D1/R2