Deletes a story from Storyblok
AI agents call delete-story to permanently remove resources in MCP Storyblok Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible operation that removes data permanently from the CMS. Deletion cannot be undone without restore capabilities, making it Destructive rather than Write. The severity is high because unintended deletion of stories could result in significant content loss and require recovery procedures. Confidence is high due to the explicit language in both the tool name and description.
From the tool's definition Tool name 'delete-story' and description 'Deletes a story from Storyblok' indicate irreversible deletion of content.
Attacks that exploit this kind of access
Deletes a story from Storyblok. It is categorised as a Destructive tool in the MCP Storyblok Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Storyblok 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 MCP Storyblok 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 MCP Storyblok Server MCP server (zerdos/mcp-storyblok-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →