delete_component
A destructive tool on the Storyblok MCP server.
This record as markdown: /tools/arjuncodess-storyblok-mcp/delete-component.md
What delete_component does on Storyblok MCP Server
AI agents call delete_component 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_component is rated Critical
Although the description is empty, the tool name unambiguously indicates deletion of a component in Storyblok CMS. In a content management system, deleting a component is an irreversible action that destroys data and could affect multiple stories or content items that reference that component. This classifies as Destructive rather than Write because the operation cannot be reversed (unlike create/update operations).
From the tool's definition Tool name 'delete_component' indicates irreversible deletion of data. The verb 'delete' in the context of a CMS explicitly describes a destructive operation that cannot be undone.
Attacks that exploit this kind of access
The rule that runs delete_component 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_component, this is the rule to start with:
delete_component 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_component call is checked against it from then on.
Questions about delete_component
delete_component 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_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 Storyblok MCP 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 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