Delete an invoice. Permanently removes the invoice. Requires Id and SyncToken.
AI agents call delete_invoice to permanently remove resources in Mcp Afip — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes invoice records from an Argentine tax authority system. Invoices are legally mandated financial/tax documents; their deletion cannot be undone and destroys audit trails and financial records. This is the most severe category (Destructive > Financial > Execute > Write > Read) because the deletion itself is the primary action, making it Destructive rather than merely Financial.
From the tool's definition 'Permanently removes the invoice' — explicit statement of irreversible deletion of financial records.
Documented attack patterns abuse exactly the kind of access delete_invoice 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 delete_invoice:
{
"version": "1",
"default": "deny",
"hide": [
"delete_invoice"
]
} delete_invoice disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an invoice. Permanently removes the invoice. Requires Id and SyncToken. It is categorised as a Destructive tool in the Mcp Afip MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for delete_invoice: 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.
delete_invoice is a Destructive 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 delete_invoice 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 delete_invoice. 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.
delete_invoice 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.