delete_webhook

A destructive tool on the Storyblok MCP server.

SERVERStoryblok MCP Server SOURCEarjuncodess/storyblok-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arjuncodess-storyblok-mcp/delete-webhook.md

WHAT IT DOES

What delete_webhook does on Storyblok MCP Server

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

RISK

Why delete_webhook is rated Critical

Deleting a webhook removes an integration endpoint permanently and cannot be undone without manual reconfiguration. This is a destructive operation that affects system integrations. While not as critical as deleting content itself, it causes loss of configuration state.

From the tool's definition Tool name 'delete_webhook' explicitly indicates deletion of a webhook configuration. No description provided, but the verb 'delete' combined with 'webhook' indicates irreversible removal of a resource.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_webhook safely

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

delete_webhook Hidden

delete_webhook 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": [
    "delete_webhook"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_webhook

What does the delete_webhook tool do? +

delete_webhook is a destructive tool on the Storyblok MCP Server MCP server. It is categorised as a Destructive tool in the Storyblok MCP Server 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? +

Register the Storyblok 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 Storyblok MCP Server. Nothing to install.

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

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.

What MCP server provides delete_webhook? +

delete_webhook is provided by the Storyblok MCP Server MCP server (arjuncodess/storyblok-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Storyblok MCP Server, and thousands of servers like it.

This server

All 115 Storyblok MCP Server 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 →