Zero-dollar authorization to validate a card without charging (card or CardToken)
AI agents use zero_auth to commit financial operations through Mcp Afip — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Although no actual charge is made, this tool performs a financial authorization against a payment card or token, which is a financial operation that touches payment infrastructure. Misuse could be used to validate stolen card credentials at scale, constituting a high-severity financial risk. The presence of sibling tools like activate_subscription and add_cart further confirms a financial/commerce context.
From the tool's definition Zero-dollar authorization to validate a card without charging (card or CardToken)
Documented attack patterns abuse exactly the kind of access zero_auth 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 zero_auth:
{
"version": "1",
"default": "deny",
"tools": {
"zero_auth": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to zero_auth is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Zero-dollar authorization to validate a card without charging (card or CardToken). It is categorised as a Financial tool in the Mcp Afip MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for zero_auth: 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.
zero_auth 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 zero_auth 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 zero_auth. 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.
zero_auth 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.