Critical Risk →

cancel_cte

Cancel an authorized CTe

How to control cancel_cte ↓

What cancel_cte does on Mcp Afip

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

Canceling an authorized electronic transport document is a destructive action because it permanently invalidates a financial/legal record that has already been issued and authorized by the tax authority. This cannot be reversed without creating a new document and is more severe than a simple write operation.

From the tool's definition Tool name 'cancel_cte' with description 'Cancel an authorized CTe'. CTe (Conocimiento de Transporte Electrónico) is an electronic transport document in the Argentine AFIP system.

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

How to control cancel_cte

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

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

cancel_cte 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_cte

What does the cancel_cte tool do? +

Cancel an authorized CTe. 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_cte? +

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

cancel_cte 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_cte? +

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

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

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