execute_x402_endpoint

Execute an x402 API endpoint. Payment is handled automatically. Supported sources: - x402.biwas.xyz (default): Use path like

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server
Critical RISK CLASS
Category Financial
Parameters 00 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/execute-x402-endpoint.md

What execute_x402_endpoint does on Aibtc

AI agents use execute_x402_endpoint to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Why execute_x402_endpoint is rated Critical

The tool explicitly states that 'payment is handled automatically' when executing x402 API endpoints. x402 is a payment protocol built on HTTP 402 (Payment Required), meaning this tool can autonomously trigger financial transactions.

From the tool's definition Execute an x402 API endpoint. Payment is handled automatically.

Questions about execute_x402_endpoint

What does the execute_x402_endpoint tool do? +

Execute an x402 API endpoint. Payment is handled automatically. Supported sources: - x402.biwas.xyz (default): Use path like. It is categorised as a Financial tool in the Aibtc MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on execute_x402_endpoint? +

Register the Aibtc MCP server in PolicyLayer and add a rule for execute_x402_endpoint: 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 Aibtc. Nothing to install.

What risk level is execute_x402_endpoint? +

execute_x402_endpoint 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 execute_x402_endpoint? +

Yes. Add a rate_limit block to the execute_x402_endpoint 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 execute_x402_endpoint completely? +

Set action: deny in the PolicyLayer policy for execute_x402_endpoint. 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 execute_x402_endpoint? +

execute_x402_endpoint is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Aibtc, 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 Aibtc'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.