pay_request
Make an HTTP request to a URL. If it returns 402 (Payment Required),
This record as markdown: /tools/io-github-pay-skill-pay-mcp/pay-request.md
What pay_request does on Pay Mcp
AI agents use pay_request to commit financial operations through Pay Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why pay_request is rated Critical
This tool is Financial because it facilitates USDC cryptocurrency payments on the Base blockchain. Even though the description is incomplete, the context establishes this as a payment system. An AI agent misusing this could send unauthorized payments, drain wallets, or commit financial fraud. Severity is critical due to direct monetary loss potential and irreversibility of blockchain transactions.
From the tool's definition Server description explicitly states 'USDC payments for AI agents on Base' and tool name 'pay_request' is part of payment infrastructure. Sibling tools include 'pay_send', 'pay_fund', 'pay_tab_charge', 'pay_tab_topup' which all commit financial transactions.
Attacks that exploit this kind of access
The rule that runs pay_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pay Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pay_request, this is the rule to start with:
Any call to pay_request is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Pay Mcp, apply this rule, and every pay_request call is checked against it from then on.
Questions about pay_request
Make an HTTP request to a URL. If it returns 402 (Payment Required),. It is categorised as a Financial tool in the Pay Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Pay MCP server in PolicyLayer and add a rule for pay_request: 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 Pay Mcp. Nothing to install.
pay_request 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 pay_request 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 pay_request. 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.
pay_request is provided by the Pay MCP server (@pay-skill/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pay, and thousands of servers like it.
Across the catalogue