AI agents call delete_space_role 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.
The tool name clearly contains 'delete', which is a core indicator of destructive operations that cannot be undone. Deleting a space role removes permissions/access configurations irreversibly. While the description is empty (lowering confidence slightly from critical to high), the destructive intent from the name itself is unambiguous.
From the tool's definition Tool name is 'delete_space_role' which explicitly performs a delete operation on a space role entity in the Storyblok CMS. No description provided, but 'delete' terminology indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_space_role gives an agent:
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_space_role:
{
"version": "1",
"default": "deny",
"hide": [
"delete_space_role"
]
}delete_space_role disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_space_role. 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_space_role: 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_space_role 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_space_role 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_space_role. 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_space_role 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.
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.
Free to start. No card required.
115 Storyblok MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.