Critical Risk →

delete_webhook

Delete a webhook subscription. Pass the webhook ID from list_webhooks. Requires authentication.

Handles credentials or secrets (apiKey)

Part of the Timergy MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@timergy/mcp Destructive

AI agents may call delete_webhook to permanently remove or destroy resources in Timergy. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call delete_webhook in a loop, permanently destroying resources in Timergy. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

timergy.yaml
tools:
  delete_webhook:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Timergy policy for all 22 tools.

Tool Name delete_webhook
Category Destructive
MCP Server Timergy MCP Server
Risk Level Critical

View all 22 tools →

Agents calling destructive-class tools like delete_webhook have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

delete_webhook is one of the critical-risk operations in Timergy. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the delete_webhook tool do? +

Delete a webhook subscription. Pass the webhook ID from list_webhooks. Requires authentication.. It is categorised as a Destructive tool in the Timergy 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 delete_webhook? +

Add a rule in your Intercept YAML policy under the tools section for delete_webhook. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Timergy MCP server.

What risk level is delete_webhook? +

delete_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 delete_webhook? +

Yes. Add a rate_limit block to the delete_webhook rule in your Intercept 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 delete_webhook completely? +

Set action: deny in the Intercept 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.

What MCP server provides delete_webhook? +

delete_webhook is provided by the Timergy MCP server (@timergy/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.