Void (release) an unsettled authorization via POST /v2/payments/authorizations/{id}/void. Use when funds were authorized but will not be captured. Returns 204 No Content on success.
AI agents use void_authorization to commit financial operations through Mcp Afip — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool cancels a financial authorization, releasing previously held funds. It directly affects payment/financial operations by voiding an authorization, which is an irreversible financial action that cannot be undone once processed. This falls squarely in the Financial category as it manipulates payment authorizations.
From the tool's definition Void (release) an unsettled authorization via POST /v2/payments/authorizations/{id}/void. Use when funds were authorized but will not be captured.
Documented attack patterns abuse exactly the kind of access void_authorization 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 void_authorization:
{
"version": "1",
"default": "deny",
"tools": {
"void_authorization": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to void_authorization is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Void (release) an unsettled authorization via POST /v2/payments/authorizations/{id}/void. Use when funds were authorized but will not be captured. Returns 204 No Content on success. 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 void_authorization: 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.
void_authorization 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 void_authorization 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 void_authorization. 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.
void_authorization 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.