Delete a webhook.site endpoint and all its data.
AI agents call delete_webhook to permanently remove resources in Webhook Site MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a webhook endpoint and all associated request data without the ability to recover it. Deletion is an irreversible operation that cannot be undone, fitting the Destructive category.
From the tool's definition Tool name 'delete_webhook' combined with description 'Delete a webhook.site endpoint and all its data' explicitly indicates irreversible deletion of data.
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 Webhook Site MCP Server, 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.site endpoint and all its data. It is categorised as a Destructive tool in the Webhook Site MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Webhook Site MCP Server 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 Webhook Site MCP Server. 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 Webhook Site MCP Server MCP server (zebbern/webhook-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Webhook Site MCP Server, 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.
23 Webhook Site MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.