Apply treasury policy to a proposed action and return allow, deny, or allow-with-limits. Paid via x402.
Part of the ActionGate server.
Free to start. No card required.
AI agents call policy_gate to retrieve information from ActionGate without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though policy_gate only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"policy_gate": {}
}
}See the full ActionGate policy for all 3 tools.
These attack patterns abuse exactly the kind of access policy_gate gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Apply treasury policy to a proposed action and return allow, deny, or allow-with-limits. Paid via x402.. It is categorised as a Read tool in the ActionGate MCP Server, which means it retrieves data without modifying state.
Register the ActionGate MCP server in PolicyLayer and add a rule for policy_gate: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ActionGate. Nothing to install.
policy_gate is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the policy_gate rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for policy_gate. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
policy_gate is provided by the ActionGate MCP server (actiongate/actiongate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 ActionGate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.