Make an HTTP request with built-in x402 payment handling. If the server returns 402 Payment Required, inspects payment requirements and optionally pays. When autoPay is enabled the tool previews the payment offer first, then makes a single paid retry. Requires configured wallet (via configure_wal...
Accepts URL/endpoint input (url); Accepts raw HTML/template content (body); Single-target operation
Part of the Agent0 MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call x402_request to retrieve information from Agent0 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 x402_request 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.
tools:
x402_request:
rules:
- action: allowSee the full Agent0 policy for all 34 tools.
Agents calling read-class tools like x402_request have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Make an HTTP request with built-in x402 payment handling. If the server returns 402 Payment Required, inspects payment requirements and optionally pays. When autoPay is enabled the tool previews the payment offer first, then makes a single paid retry. Requires configured wallet (via configure_wallet) with USDC on a supported payment chain.. It is categorised as a Read tool in the Agent0 MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for x402_request. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Agent0 MCP server.
x402_request 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 x402_request 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 x402_request. 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.
x402_request is provided by the Agent0 MCP server (@rickydata/agent0-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept