Generate a static (reusable) Nequi QR code for a merchant
AI agents use create_static_qr 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.
The tool creates new payment infrastructure (a QR code) that can be used repeatedly for transactions. This is a Write operation as it creates a reversible asset. Severity is medium because while the QR code itself is not destructive, misuse could enable fraudulent payment collection if an attacker generates QR codes pointing to attacker-controlled accounts.
From the tool's definition Tool description states 'Generate a static (reusable) Nequi QR code for a merchant' — this creates a new, reusable payment QR code artifact that persists for future use.
Documented attack patterns abuse exactly the kind of access create_static_qr 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 create_static_qr:
{
"version": "1",
"default": "deny",
"tools": {
"create_static_qr": {
"limits": [
{
"counter": "create_static_qr_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_static_qr 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 (reusable) Nequi QR code for a merchant. 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 create_static_qr: 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.
create_static_qr 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 create_static_qr 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 create_static_qr. 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.
create_static_qr 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.