delete_story
A destructive tool on the Storyblok MCP server.
This record as markdown: /tools/arjuncodess-storyblok-mcp/delete-story.md
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.
Why delete_story is rated Critical
Despite the empty description, the function name 'delete_story' unambiguously indicates this tool permanently removes story content from the CMS. This is an irreversible action that cannot be undone, fitting the Destructive category. The high severity reflects that an AI agent invoking this tool could permanently erase valuable content from the CMS. Confidence is high due to the explicit naming convention.
From the tool's definition Tool name is 'delete_story' which directly indicates irreversible deletion of data. The name clearly conveys a destructive operation targeting story content in the Storyblok CMS.
Attacks that exploit this kind of access
The rule that runs delete_story 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_story, this is the rule to start with:
delete_story is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Storyblok MCP Server, apply this rule, and every delete_story call is checked against it from then on.
Questions about delete_story
delete_story 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.
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.
delete_story is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
delete_story 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.
More on Storyblok MCP Server, and thousands of servers like it.
Across the catalogue