x402_pay
Pay an external API or service via the x402 protocol (HTTP 402). MIDAS handles payment signing and settlement automatically using your Base wallet USDC.
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/x402-pay.md
What x402_pay does on MIDAS Protocol
AI agents use x402_pay to commit financial operations through MIDAS Protocol, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | |
body | string | — | |
method | string | — | |
headers | object | — |
Parameters from the server's own tool schema.
Why x402_pay is rated Critical
This tool moves money (USDC tokens) from a wallet, committing financial obligations and transferring value. Financial transactions represent the highest-severity category and carry critical risk if an AI agent misuses them without proper authorization or context—funds could be transferred to unintended recipients or for unintended services.
From the tool's definition Tool description explicitly states: 'Pay an external API or service via the x402 protocol' and 'using your Base wallet USDC.' The tool name 'x402_pay' directly indicates payment functionality.
Risk signalsAccepts URL/endpoint input (url) · Accepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs x402_pay safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MIDAS Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For x402_pay, this is the rule to start with:
Any call to x402_pay is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MIDAS Protocol, apply this rule, and every x402_pay call is checked against it from then on.
Questions about x402_pay
Pay an external API or service via the x402 protocol (HTTP 402). MIDAS handles payment signing and settlement automatically using your Base wallet USDC. It is categorised as a Financial tool in the MIDAS Protocol MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
x402_pay accepts 4 parameters: url, body, method, headers. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for x402_pay: 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 MIDAS Protocol. Nothing to install.
x402_pay is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the x402_pay 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 x402_pay. 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_pay is provided by the MIDAS Protocol MCP server (https://mcp.midasprotocol.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MIDAS Protocol, and thousands of servers like it.
Across the catalogue