MCP gateway · the tool boundary (Beta)
Authorize every MCP tool call.
Runs in your environment, between your MCP client and an upstream MCP server. Point your client at the gateway; every tool call is classified by deterministic rules, evaluated against your policy, and either authorized with a token or refused before it reaches the server. No AI model is involved. Beta — stdio and streamable-HTTP.
02 · What you get
Proxied tool calls
The gateway you run asks Intended for a decision, then forwards allowed calls to your upstream MCP server. Intended never sees your upstream credentials or calls the server itself. Point your client at the gateway (a config change). It runs over stdio or streamable-HTTP.
Per-tool evaluation
Each tool call is interpreted into an IntentRequest and evaluated against your policy. Deny means the call never reaches the upstream server.
Authority Tokens in-line
Approved calls receive an Authority Token attached to the upstream request. Verified at the tool boundary.
Every call sealed
Decision, rationale, tool and a description of the call recorded in your hash-linked audit chain. See what is stored and where MCP data goes.