Get x402 crypto funding info for your wallet. Returns the endpoint URL, network, and setup instructions. To actually pay, your HTTP client needs @x402/fetch which automatically handles the 402 payment flow with USDC. This is the fully autonomous funding method — no human needed.
AI agents use fund_wallet_x402 to commit financial operations through AgentPay — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool facilitates crypto (USDC) payment transactions for funding a wallet autonomously. Even though it returns funding info/instructions, it is explicitly part of a payment flow that commits financial obligations by moving cryptocurrency. The 'fully autonomous funding method — no human needed' aspect raises the blast radius to critical, as an AI agent could misuse this to fund wallets without human oversight.
From the tool's definition 'fund_wallet_x402' — 'Get x402 crypto funding info for your wallet', 'automatically handles the 402 payment flow with USDC', 'fully autonomous funding method — no human needed'
Attacks that exploit this kind of access
Get x402 crypto funding info for your wallet. Returns the endpoint URL, network, and setup instructions. To actually pay, your HTTP client needs @x402/fetch which automatically handles the 402 payment flow with USDC. This is the fully autonomous funding method — no human needed. It is categorised as a Financial tool in the AgentPay MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the AgentPay MCP server in PolicyLayer and add a rule for fund_wallet_x402: 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 AgentPay. Nothing to install.
fund_wallet_x402 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 fund_wallet_x402 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 fund_wallet_x402. 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.
fund_wallet_x402 is provided by the AgentPay MCP server (joepangallo/mcp-server-agentpay). 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 →