Get Pix QR code for a payment (returns payload and image)
AI agents use get_pix_qrcode to commit financial operations through Mcp Ap2 — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Pix QR codes are payment instruments; generating one is the first step in committing a financial transaction. Even though the tool itself returns a code rather than executing the transfer, it creates a binding payment request in the Pix protocol context. The server is explicitly described as handling payments (AP2 — Agent-to-Agent Payment Protocol), elevating this to Financial category.
From the tool's definition 'Get Pix QR code for a payment (returns payload and image)' — directly initiates a Pix payment flow by generating a payment QR code payload
Documented attack patterns abuse exactly the kind of access get_pix_qrcode gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for get_pix_qrcode:
{
"version": "1",
"default": "deny",
"tools": {
"get_pix_qrcode": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to get_pix_qrcode is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Get Pix QR code for a payment (returns payload and image). It is categorised as a Financial tool in the Mcp Ap2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for get_pix_qrcode: 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 Mcp Ap2. Nothing to install.
get_pix_qrcode 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 get_pix_qrcode 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 get_pix_qrcode. 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.
get_pix_qrcode is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.