Govern MCP tools
Put a policy check between an MCP client and external tool execution.
The Model Context Protocol connects clients
such as Claude Desktop to tool servers. The Thoth MCP proxy checks tools/call
requests before forwarding permitted actions to the upstream MCP server.
Choose your integration
The proxy needs a configured environment, authenticated identity, and server policy. It is separate from the developer SDK trial. Its endpoint registration and routing contract is documented in the proxy guide.
Build a custom MCP client
If your application calls MCP tools itself, use the Python, TypeScript, or Go SDK to wrap the callback that actually sends the tool call. Dispatch through the governed function; calling the raw MCP session directly bypasses that wrapper.
Start with Your first governed agent before connecting a real server. Then instrument your own agent with stable tool names, actor context, and a policy agreed with your administrator. The model's choice of tool is request input, not permission to execute it.
Handle decisions and evidence
ALLOW permits forwarding. STEP_UP pauses for configured approval.
BLOCK refuses the call. Verify each required outcome in your environment,
including denial and expiry for approvals. Collect and correlate available
decision records and behavioral events separately; event delivery does not
by itself verify a signed receipt.
Configure Thoth itself
The MCP proxy governs external MCP traffic. It does not expose tools that configure Thoth. Use Terraform, Pulumi, or supported control-plane CLI/API workflows to manage governance settings.