Critical Risk →

delete_story

Deletes a story by ID.

How to control delete_story ↓

What delete_story does on Storyblok MCP Server

AI agents call delete_story 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.

Critical Risk

Why delete_story needs a policy

The tool permanently removes a story from the Storyblok space. Deletion is irreversible and cannot be undone through the tool's normal operation. This represents a destructive action with significant blast radius in a CMS context, as deleted stories may contain valuable content.

From the tool's definition Tool name 'delete_story' and description 'Deletes a story by ID' explicitly indicate irreversible deletion of data.

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

How to control delete_story

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_story:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_story"
  ]
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_story

What does the delete_story tool do? +

Deletes a story by ID. 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_story? +

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

delete_story 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_story? +

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

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

delete_story 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.

Free to start. No card required.

159 Storyblok MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.