q402_request_create
Publish a Q402 payment request (an invoice / bill). Moves no funds - it creates a shareable
This record as markdown: /tools/io-github-bitgett-q402-mcp/q402-request-create.md
What q402_request_create does on Q402 Mcp
AI agents use q402_request_create to create or update resources in Q402 Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Q402 Mcp environment.
Why q402_request_create is rated Medium
This tool creates (Write) a new payment request object that can be shared, which is a reversible data creation action. It explicitly does not move funds, so it is not Financial. However, the context of a payment system where this creates binding invoices/bills that obligate payment introduces moderate risk if an agent creates unauthorized payment requests on behalf of a user.
From the tool's definition Tool description states it 'Publish a Q402 payment request (an invoice / bill). Moves no funds - it creates a shareable'. The action is to create and publish a payment request artifact.
Attacks that exploit this kind of access
The rule that runs q402_request_create 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_request_create, this is the rule to start with:
q402_request_create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Q402 Mcp, apply this rule, and every q402_request_create call is checked against it from then on.
Questions about q402_request_create
Publish a Q402 payment request (an invoice / bill). Moves no funds - it creates a shareable. It is categorised as a Write tool in the Q402 Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Q402 MCP server in PolicyLayer and add a rule for q402_request_create: 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_request_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the q402_request_create 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_request_create. 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_request_create 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.
This server
Across the catalogue