Unpublishes a story in Storyblok
AI agents use unpublish-story to create or update resources in MCP Storyblok Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Storyblok Server environment.
Unpublishing a story reverses its public visibility but does not delete it — the content remains in the CMS and can be republished. This is a reversible state change, making it a Write operation. However, severity is high because taking live content offline can have significant impact on production websites or applications relying on that content being published.
From the tool's definition Unpublishes a story in Storyblok
Attacks that exploit this kind of access
Unpublishes a story in Storyblok. It is categorised as a Write tool in the MCP Storyblok Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Storyblok Server MCP server in PolicyLayer and add a rule for unpublish-story: 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 MCP Storyblok Server. Nothing to install.
unpublish-story is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unpublish-story 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 unpublish-story. 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.
unpublish-story is provided by the MCP Storyblok Server MCP server (zerdos/mcp-storyblok-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →