EXECUTE the purchase and show the qrcode image in the response. Use this tool ONLY AFTER the user has selected a specific payment plan from the tool list_payment_plans, offers from the tool list_checkout_offers and quantity. After this tool is used, show the payment status and qrcode image in the...
AI agents use createPayment to commit financial operations through Customer Registration MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly executes payments and financial transactions, moving money or committing financial obligations. It is the most severe category applicable. The instruction to use it 'ONLY AFTER' plan/offer selection confirms intentionality, but an AI agent with access could still misuse it by selecting arbitrary plans and executing payments without proper authorization or user confirmation, creating significant…
From the tool's definition Tool description explicitly states 'EXECUTE the purchase' and references showing QR codes and payment links (pix/bank_slip), indicating it commits financial transactions.
Attacks that exploit this kind of access
EXECUTE the purchase and show the qrcode image in the response. Use this tool ONLY AFTER the user has selected a specific payment plan from the tool list_payment_plans, offers from the tool list_checkout_offers and quantity. After this tool is used, show the payment status and qrcode image in the response if it is pix or the link for download if it is bank_slip. In both cases, the status should be. It is categorised as a Financial tool in the Customer Registration MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Customer Registration MCP Server MCP server in PolicyLayer and add a rule for createPayment: 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 Customer Registration MCP Server. Nothing to install.
createPayment 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 createPayment 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 createPayment. 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.
createPayment is provided by the Customer Registration MCP Server MCP server (rodrigoai/mcpnova). 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 →