Fetch data from a website or API. Automatically handles payment if required (402 status).
AI agents use fetch-with-payment to commit financial operations through AI42-MCP X402 Payment Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool can autonomously initiate Solana cryptocurrency payments when a 402 Payment Required response is encountered. Although it also fetches data (Read), the dominant risk is Financial — an AI agent could trigger real monetary transactions up to the spending limit without explicit per-payment human approval.
From the tool's definition 'Automatically handles payment if required (402 status)' and server description states 'automatic X402 payment handling using Solana' with 'configurable spending limits'
Attacks that exploit this kind of access
Fetch data from a website or API. Automatically handles payment if required (402 status). It is categorised as a Financial tool in the AI42-MCP X402 Payment Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the AI42-MCP X402 Payment Server MCP server in PolicyLayer and add a rule for fetch-with-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 AI42-MCP X402 Payment Server. Nothing to install.
fetch-with-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 fetch-with-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 fetch-with-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.
fetch-with-payment is provided by the AI42-MCP X402 Payment Server MCP server (kishore-mk/ai42-mcp). 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 →