execute_destructive

THE RISK

Critical Risk

Why execute_destructive needs a policy

The tool is explicitly named and described as 'destructive', indicating it performs irreversible delete/overwrite operations on Storyblok content. The description is truncated but the name alone combined with the server context (content management API) strongly implies destructive operations like deleting stories, assets, or spaces.

From the tool's definition Tool name 'execute_destructive' and description 'Execute a destructive Storyblok API operation. Use for operations with behavior'

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

POLICY

How to control execute_destructive

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 execute_destructive:

policy.json

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

execute_destructive 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

Write execute Execute a mutating Storyblok API operation. Use for operations with behavior: Write upload_asset Upload an asset to Storyblok in a single operation. Handles the Storyblok asset record cre Read execute_readonly Execute a read-only Storyblok API operation. Use for operations with behavior: Read search Search for available Storyblok API endpoints. Returns operations with their operationId, b

All 5 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

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 →

FAQ

Questions about execute_destructive

What does the execute_destructive tool do? +

Execute a destructive Storyblok API operation. Use for operations with behavior:. 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 execute_destructive? +

Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for execute_destructive: 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 execute_destructive? +

execute_destructive 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 execute_destructive? +

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

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

execute_destructive is provided by the Storyblok MCP Server MCP server (storyblok/mcp-server). 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 →