AI agents call delete_webhook to permanently remove resources in Airtable MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Webhooks are persistent infrastructure configurations used to trigger automations and integrations. Deleting a webhook irreversibly breaks those automations and cannot be recovered without manually recreating the webhook. This falls squarely into the Destructive category (irreversibly deletes or overwrites data, or actions that cannot be undone) rather than Write (which is reversible).
From the tool's definition delete_webhook" permanently removes a webhook configuration, which is an irreversible deletion operation. The description explicitly states "Delete a webhook", and deletion is a destructive action that cannot be undone.
Documented attack patterns abuse exactly the kind of access delete_webhook gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Airtable MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_webhook:
{
"version": "1",
"default": "deny",
"hide": [
"delete_webhook"
]
} delete_webhook disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a webhook. It is categorised as a Destructive tool in the Airtable MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Airtable MCP server in PolicyLayer and add a rule for delete_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 Airtable MCP. Nothing to install.
delete_webhook is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_webhook is provided by the Airtable MCP server (rashidazarang/airtable-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 45 Airtable MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
45 Airtable MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.