Create a new tag in your Storyblok space and add it to a story
AI agents use create-tag-and-add-to-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 tag and adding it to a story are write operations that modify content metadata reversibly. This is less severe than destructive operations (tags/associations can be undone) and does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool name and description indicate 'create' (new tag) and 'add' (to story) operations. These are reversible modifications: tags can be removed and deleted, stories can be re-tagged.
Attacks that exploit this kind of access
Create a new tag in your Storyblok space and add it to a story. 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-tag-and-add-to-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-tag-and-add-to-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-tag-and-add-to-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-tag-and-add-to-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-tag-and-add-to-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 →