Call a Gateway route with caller-supplied auth/payment headers. MCP does not sign, pay, or execute wallet commands. Devnet routes expect devnet-USDC payment headers; mainnet routes expect mainnet-USDC headers; Tokens API SIWX routes are free.
Accepts file system path (path); Accepts freeform code/query input (query); Accepts raw HTML/template content (body)
Part of the Gateway MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke agon_gateway_call_with_headers to trigger processes or run actions in Gateway. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
agon_gateway_call_with_headers can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
agon_gateway_call_with_headers:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Gateway policy for all 15 tools.
Agents calling execute-class tools like agon_gateway_call_with_headers have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
agon_gateway_call_with_headers is one of the high-risk operations in Gateway. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Call a Gateway route with caller-supplied auth/payment headers. MCP does not sign, pay, or execute wallet commands. Devnet routes expect devnet-USDC payment headers; mainnet routes expect mainnet-USDC headers; Tokens API SIWX routes are free.. It is categorised as a Execute tool in the Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for agon_gateway_call_with_headers. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Gateway MCP server.
agon_gateway_call_with_headers is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the agon_gateway_call_with_headers rule in your Intercept 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 Intercept policy for agon_gateway_call_with_headers. 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.
agon_gateway_call_with_headers is provided by the Gateway MCP server (@agonx402/gateway-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.