delete_component

THE RISK

Critical Risk

Why delete_component needs a policy

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.

Documented attack patterns abuse exactly the kind of access delete_component gives an agent:

POLICY

How to control delete_component

PolicyLayer is an MCP gateway — it sits between your AI agents and Storyblok MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_component:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_component"
  ]
}

delete_component disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Storyblok MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Storyblok MCP Server tools

Destructive delete_access_token delete_access_token Destructive delete_asset delete_asset Destructive delete_asset_folder delete_asset_folder Destructive delete_branch delete_branch Destructive delete_component_folder delete_component_folder Destructive delete_datasource delete_datasource Destructive delete_datasource_entry delete_datasource_entry Destructive delete_preset delete_preset

All 115 Storyblok MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Govern database agents → Read-only defaults, blocked table drops, and no DELETE without a WHERE clause on every query.
Critical-risk tools in Storyblok MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about delete_component

What does the delete_component tool do? +

delete_component. 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_component? +

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.

What risk level is delete_component? +

delete_component 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_component? +

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.

How do I block delete_component completely? +

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.

What MCP server provides delete_component? +

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.

Enforce policy on every Storyblok MCP Server tool call.

Start from Storyblok MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →