AI agents use generateStaticPix to commit financial operations through Pix — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool generates Pix payment QR codes used in the Brazilian instant payment system. Creating a Pix QR code directly facilitates financial transactions — a recipient scanning the code would transfer money. Misuse could redirect payments to attacker-controlled keys or generate fraudulent payment requests, making this a Financial category tool with high severity.
From the tool's definition Generate a static Pix QR code for any Pix key... Brazilian payments... EMV 4.0 compliance
Attacks that exploit this kind of access
Generate a static Pix QR code for any Pix key (works without API credentials). It is categorised as a Financial tool in the Pix MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Pix MCP server in PolicyLayer and add a rule for generateStaticPix: 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 Pix. Nothing to install.
generateStaticPix 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 generateStaticPix 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 generateStaticPix. 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.
generateStaticPix is provided by the Pix MCP server (regenerating-world/pix-mcp). 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 →