Critical Risk →

delete_card

Detach a saved card from its customer (DELETE /cards/{id}). The card id becomes unusable as source_id afterwards.

How to control delete_card ↓

What delete_card does on Mcp Afip

AI agents call delete_card 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 delete_card needs a policy

This tool irreversibly deletes payment method data associated with a customer account. While not directly moving money, it destroys stored financial credentials that cannot be recovered. The permanent nature (card becomes unusable) and the financial context (AFIP payment card management) classify this as Destructive rather than Write.

From the tool's definition Tool description explicitly states 'Detach a saved card' and uses DELETE HTTP method. The card ID 'becomes unusable as source_id afterwards' indicates the action is irreversible and permanently removes the card from the system.

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

How to control delete_card

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

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

delete_card 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 delete_card

What does the delete_card tool do? +

Detach a saved card from its customer (DELETE /cards/{id}). The card id becomes unusable as source_id afterwards. 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 delete_card? +

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

delete_card 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 delete_card? +

Yes. Add a rate_limit block to the delete_card 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 delete_card completely? +

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

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