Critical Risk →

revoke_agent

Revoke an agent

How to control revoke_agent ↓

What revoke_agent does on Mcp Afip

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

Revoking an agent in the AFIP electronic invoicing context means removing the agent's authorization to act on behalf of a taxpayer. This is effectively irreversible (or at minimum highly disruptive) as it cancels a delegation of authority. The action cannot be trivially undone and could disrupt all electronic invoicing operations the agent was authorized to perform, making it Destructive with high severity.

From the tool's definition 'Revoke an agent' — revoking an agent removes authorization/access irreversibly

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

How to control revoke_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 revoke_agent:

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

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

What does the revoke_agent tool do? +

Revoke an agent. 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 revoke_agent? +

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

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

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

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

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