Critical Risk →

unsubscribe_webhook

Remove a previously registered webhook

How to control unsubscribe_webhook ↓

What unsubscribe_webhook does on Mcp Afip

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

Removing a webhook is an irreversible deletion of a configured integration endpoint. Once removed, event notifications to that endpoint will cease and the registration is gone, which cannot be undone without re-registering. This fits the Destructive category.

From the tool's definition 'Remove a previously registered webhook' — permanently deletes a webhook registration

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

How to control unsubscribe_webhook

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

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

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

What does the unsubscribe_webhook tool do? +

Remove a previously registered webhook. 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 unsubscribe_webhook? +

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

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

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

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

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