q402_pay
USE THIS TOOL whenever the user asks to send, transfer, or pay USDC / USDT /
This record as markdown: /tools/io-github-bitgett-q402-mcp/q402-pay.md
What q402_pay does on Q402 Mcp
AI agents use q402_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_pay is rated Critical
This tool directly commits financial obligations by transferring cryptocurrency assets. Even though it is described as 'gasless' and operates on a 'Sandbox-default' environment, the core function is to move money between accounts.
From the tool's definition Tool description explicitly states 'send, transfer, or pay USDC / USDT'; context indicates Q402 is a gasless payment system on EVM chains. The tool facilitates direct movement of stablecoins (USDC/USDT).
Attacks that exploit this kind of access
The rule that runs q402_pay safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Q402 Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For q402_pay, this is the rule to start with:
Any call to q402_pay is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Q402 Mcp, apply this rule, and every q402_pay call is checked against it from then on.
Questions about q402_pay
USE THIS TOOL whenever the user asks to send, transfer, or pay USDC / USDT /. 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.
Register the Q402 MCP server in PolicyLayer and add a rule for q402_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.
q402_pay 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 q402_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.
Set action: deny in the PolicyLayer policy for q402_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.
q402_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.
Across the catalogue