bulk-delete-stories

Deletes multiple stories in Storyblok

Server MCP Storyblok Server zerdos/mcp-storyblok-server
Category Destructive
Risk class Critical
Parameters 00 required

What bulk-delete-stories does on MCP Storyblok Server

AI agents call bulk-delete-stories 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.

Why bulk-delete-stories needs a policy

This tool permanently removes stories from the CMS without possibility of reversal. Deletion operations that cannot be undone are classified as Destructive. The bulk nature increases the blast radius, justifying 'high' severity rather than 'critical' (which would apply if it could also delete system-critical or unrecoverable data).

From the tool's definition Tool name 'bulk-delete-stories' and description 'Deletes multiple stories in Storyblok' directly indicate irreversible deletion of content. The 'bulk' qualifier indicates multiple records can be deleted in a single operation.

Risk signalsBulk/mass operation — affects multiple targets

Questions about bulk-delete-stories

What does the bulk-delete-stories tool do? +

Deletes multiple stories in 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.

How do I enforce a policy on bulk-delete-stories? +

Register the MCP Storyblok Server MCP server in PolicyLayer and add a rule for bulk-delete-stories: 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.

What risk level is bulk-delete-stories? +

bulk-delete-stories 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 bulk-delete-stories? +

Yes. Add a rate_limit block to the bulk-delete-stories 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 bulk-delete-stories completely? +

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

bulk-delete-stories 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.