Creates a new story in Storyblok
AI agents use create-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.
Creating a story is a Write operation—it adds new content to the CMS that can be modified or deleted later. It's not destructive (content can be removed), not financial, and not Execute (no arbitrary code execution). Severity is medium because an agent could create unwanted stories at scale, but the damage is reversible through deletion or rollback.
From the tool's definition Tool name 'create-story' and description 'Creates a new story in Storyblok' indicate creation of new content in the CMS. This is a reversible modification operation.
Attacks that exploit this kind of access
Creates a new 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 create-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.
create-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 create-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 create-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.
create-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 →