delete_release

THE RISK

Critical Risk

Why delete_release needs a policy

This tool performs an irreversible deletion operation. Once a release is deleted, it cannot be recovered through normal operations, and any content or scheduling tied to that release is lost. This is unambiguously Destructive. Severity is high because inadvertent deletion of a release in a production CMS could disrupt content workflows, scheduled publications, or rollback capabilities.

From the tool's definition Tool name 'delete_release' with description 'Deletes a release.' The verb 'Deletes' indicates irreversible removal of data. Context shows this is part of a content management system (Storyblok) where releases represent published or scheduled content versions.

Documented attack patterns abuse exactly the kind of access delete_release gives an agent:

POLICY

How to control delete_release

PolicyLayer is an MCP gateway — it sits between your AI agents and Storyblok MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_release:

policy.json

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

delete_release disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Storyblok MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Storyblok MCP Server tools

Destructive bulk_delete_stories Deletes multiple stories in Storyblok. Destructive delete_access_token Delete an access token from the current Storyblok space using the Management API. Destructive delete_approval Deletes an approval from a specified Storyblok space. Destructive delete_asset Deletes an asset from Storyblok. Destructive delete_asset_folder Delete an asset folder from the current Storyblok space. Destructive delete_branch Deletes a branch (pipeline) by its ID in a Storyblok space. Destructive delete_collaborator Deletes a collaborator from a specified Storyblok space. Destructive delete_comment Deletes a comment from a discussion via the Storyblok Management API.

All 159 Storyblok MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Storyblok MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_release

What does the delete_release tool do? +

Deletes a release. 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_release? +

Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for delete_release: 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_release? +

delete_release 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_release? +

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

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

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

Enforce policy on every Storyblok MCP Server tool call.

Start from Storyblok MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →