webhooks_delete

Delete a webhook. Pending deliveries are cascade-deleted; in-flight HTTP attempts finish their current run.

SERVERMunin SOURCEhttps://mcp.getmunin.com/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-getmunin-munin/webhooks-delete.md

WHAT IT DOES

What webhooks_delete does on Munin

AI agents call webhooks_delete to permanently remove resources in Munin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why webhooks_delete is rated Critical

This tool permanently removes a webhook and its associated pending delivery records without possibility of recovery. While not a direct data deletion on core customer records, webhooks are critical infrastructure for event delivery and automation pipelines.

From the tool's definition 'Delete a webhook' and 'Pending deliveries are cascade-deleted' indicate irreversible removal of data and configuration with cascading side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs webhooks_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For webhooks_delete, this is the rule to start with:

webhooks_delete Hidden

webhooks_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "webhooks_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every webhooks_delete call is checked against it from then on.

FAQ

Questions about webhooks_delete

What does the webhooks_delete tool do? +

Delete a webhook. Pending deliveries are cascade-deleted; in-flight HTTP attempts finish their current run. It is categorised as a Destructive tool in the Munin 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 webhooks_delete? +

Register the Munin MCP server in PolicyLayer and add a rule for webhooks_delete: 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 Munin. Nothing to install.

What risk level is webhooks_delete? +

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

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

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

webhooks_delete is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Munin, and thousands of servers like it.

This server

All 242 Munin tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →