Deletes a component from Storyblok
AI agents call delete-component 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.
Deleting a component from a CMS is a destructive operation that cannot be undone. Components may be referenced across multiple stories and assets, so deletion could break existing content and cause cascading damage. This warrants the Destructive category and high severity due to the potential for significant content loss and the irreversible nature of the action.
From the tool's definition Tool name explicitly includes 'delete-component' and description states 'Deletes a component from Storyblok'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Deletes a component 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-component: 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-component 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-component 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-component. 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-component 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 →