New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_story

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

Questions about delete_story

What does the delete_story tool do? +

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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Storyblok MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.