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.

SERVERMIDAS Protocol SOURCEhttps://mcp.midasprotocol.org/mcp
Critical RISK CLASS
Category Financial
Parameters 41 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about x402_pay

What does the x402_pay tool do? +

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.

What parameters does x402_pay accept? +

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.

How do I enforce a policy on x402_pay? +

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.

What risk level is x402_pay? +

x402_pay is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit x402_pay? +

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.

How do I block x402_pay completely? +

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.

What MCP server provides x402_pay? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MIDAS Protocol's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.