AI agents call delete_access_token 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.
Access tokens are security credentials that cannot be recovered once deleted. Deletion is an irreversible operation that could render integrations non-functional and cannot be undone. This qualifies as Destructive rather than Write. High severity reflects that token deletion could disrupt AI agent operations or cause service outages, though impact is limited to authentication rather than data or financial assets.
From the tool's definition Tool name 'delete_access_token' indicates irreversible deletion of an authentication token. The verb 'delete' is explicitly destructive.
Documented attack patterns abuse exactly the kind of access delete_access_token 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_access_token:
{
"version": "1",
"default": "deny",
"hide": [
"delete_access_token"
]
}delete_access_token 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_access_token. 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_access_token: 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_access_token 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_access_token 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_access_token. 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_access_token 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.