New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

q402_request_pay

Pay a Q402 payment request from your own Agent Wallet, gaslessly. Give it a req_ id (from a

SERVERQ402 Mcp SOURCE@quackai/q402-mcp
Critical RISK CLASS
Category Financial
Parameters 00 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitgett-q402-mcp/q402-request-pay.md

What q402_request_pay does on Q402 Mcp

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

Why q402_request_pay is rated Critical

This tool commits financial obligations by executing payments from an Agent Wallet. It directly transfers value and constitutes a financial transaction. This is the most severe category (Financial > Destructive > Execute > Write > Read). Critical severity due to irreversible money movement and potential for unauthorized fund transfers if an AI agent misuses it with malicious or erroneous payment requests.

From the tool's definition Tool name 'q402_request_pay' and description 'Pay a Q402 payment request from your own Agent Wallet, gaslessly' explicitly indicates moving money/processing payments.

Questions about q402_request_pay

What does the q402_request_pay tool do? +

Pay a Q402 payment request from your own Agent Wallet, gaslessly. Give it a req_ id (from a. It is categorised as a Financial tool in the Q402 Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on q402_request_pay? +

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

What risk level is q402_request_pay? +

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

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

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

q402_request_pay is provided by the Q402 MCP server (@quackai/q402-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

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