Policy Gate MCP server
{
"mcpServers": {
"workers-policy-gate": {
"type": "http",
"url": "https://policy-gate.3labsio.workers.dev/mcp"
}
}
}{
"mcpServers": {
"workers-policy-gate": {
"type": "http",
"url": "https://policy-gate.3labsio.workers.dev/mcp"
}
}
}{
"mcpServers": {
"workers-policy-gate": {
"type": "http",
"url": "https://policy-gate.3labsio.workers.dev/mcp"
}
}
}{
"servers": {
"workers-policy-gate": {
"type": "http",
"url": "https://policy-gate.3labsio.workers.dev/mcp"
}
}
}{
"mcpServers": {
"workers-policy-gate": {
"type": "http",
"url": "https://policy-gate.3labsio.workers.dev/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.2.0
What it does
Policy Gate is a deterministic policy engine that classifies agent actions into allow, require_approval, or deny verdicts before execution. It is for developers building autonomous agents who need to enforce governance rules, including spending caps and approval workflows, with full auditability and no LLM in the decision path.
- Gate financial transactions by tier, requiring human approval for payments above a threshold or denying forbidden actions like exposing credentials.
- Enforce cumulative spending caps across multiple related actions by including historical ledger state in each policy check.
- Audit agent behavior deterministically, replaying the exact same policy decision weeks later with identical inputs and ledger state.
Tools this server exposes
| Tool | Does |
|---|---|
| check | Evaluates a policy, request, and optional ledger state to return a verdict (allow, require_approval, deny) and metadata about the decision. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.