Critical Risk →

cancel_debit

Cancel a debit-card payment by Getnet payment_id.

How to control cancel_debit ↓

What cancel_debit does on Mcp Afip

AI agents call cancel_debit 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.

Critical Risk

Why cancel_debit needs a policy

Although this tool involves financial data (debit-card payments), the action is irreversible cancellation of a committed transaction, which destroys the payment state. This cannot be undone by a subsequent create/write operation—it permanently voids the original debit. In a misuse scenario, an AI agent could cancel legitimate customer payments, causing immediate financial and operational harm.

From the tool's definition cancel_debit cancels a debit-card payment by payment_id. Cancellation of a payment is an irreversible financial operation that reverses a transaction.

Documented attack patterns abuse exactly the kind of access cancel_debit gives an agent:

How to control cancel_debit

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 cancel_debit:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_debit"
  ]
}

cancel_debit disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Mcp Afip — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cancel_debit

What does the cancel_debit tool do? +

Cancel a debit-card payment by Getnet payment_id. 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.

How do I enforce a policy on cancel_debit? +

Register the Mcp Afip MCP server in PolicyLayer and add a rule for cancel_debit: 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.

What risk level is cancel_debit? +

cancel_debit is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cancel_debit? +

Yes. Add a rate_limit block to the cancel_debit 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.

How do I block cancel_debit completely? +

Set action: deny in the PolicyLayer policy for cancel_debit. 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.

What MCP server provides cancel_debit? +

cancel_debit 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.

Enforce policy on every Mcp Afip tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.