Make an x402 micropayment.
AI agents use make_x402_payment to commit financial operations through Solana Trading MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly moves funds by executing a micropayment via the x402 protocol on a Solana trading server. Financial transactions are irreversible on-chain, and misuse by an AI agent could result in unauthorized fund transfers. Classified as Financial with critical severity due to the direct monetary impact and irreversibility of blockchain payments.
From the tool's definition make_x402_payment" and "Make an x402 micropayment" — explicitly initiates a payment transaction
Attacks that exploit this kind of access
Make an x402 micropayment. It is categorised as a Financial tool in the Solana Trading MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Solana Trading MCP Server MCP server in PolicyLayer and add a rule for make_x402_payment: 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 Solana Trading MCP Server. Nothing to install.
make_x402_payment 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 make_x402_payment 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 make_x402_payment. 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.
make_x402_payment is provided by the Solana Trading MCP Server MCP server (itskazgar/solana-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →