Generate a static PicPay Pay QR code for in-store / reusable use. The buyer opens PicPay, scans the QR and types in the amount. Returns the QR content and a base64 image.
AI agents use generate_static_qrcode to create or update resources in Mcp Afip — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Afip environment.
This tool creates a reusable payment QR code artifact. While it does not directly move money, it generates a financial instrument (a payment QR code) that enables financial transactions. It falls under Write as it creates a persistent/reusable artifact, but the financial facilitation aspect is notable.
From the tool's definition Generate a static PicPay Pay QR code for in-store / reusable use. Returns the QR content and a base64 image.
Documented attack patterns abuse exactly the kind of access generate_static_qrcode gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_static_qrcode:
{
"version": "1",
"default": "deny",
"tools": {
"generate_static_qrcode": {
"limits": [
{
"counter": "generate_static_qrcode_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} generate_static_qrcode 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.
Free to start. No card required.
Generate a static PicPay Pay QR code for in-store / reusable use. The buyer opens PicPay, scans the QR and types in the amount. Returns the QR content and a base64 image. It is categorised as a Write tool in the Mcp Afip MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for generate_static_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 Afip. Nothing to install.
generate_static_qrcode 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 generate_static_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 generate_static_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.
generate_static_qrcode is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Afip, 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 Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.