AI agents use publish_story to create or update resources in Storyblok MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Storyblok MCP Server environment.
Publishing is a Write operation: it changes content state from draft to published, affecting live systems visible to end users. It's reversible (can be unpublished), so not Destructive. The medium severity reflects that publishing without authorization could expose sensitive content, affect user-facing systems, or trigger unintended business workflows, but the effect is containable through rollback.
From the tool's definition Tool description states 'Publishes a Storyblok story by its ID' — publishing is a state-change operation that modifies story visibility and makes content live in production systems. While reversible via unpublish, it has significant business impact.
Documented attack patterns abuse exactly the kind of access publish_story 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 publish_story:
{
"version": "1",
"default": "deny",
"tools": {
"publish_story": {
"limits": [
{
"counter": "publish_story_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}publish_story stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Publishes a Storyblok story by its ID. It is categorised as a Write tool in the Storyblok MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for publish_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 Storyblok MCP Server. Nothing to install.
publish_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 publish_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 publish_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.
publish_story is provided by the Storyblok MCP Server MCP server (kiran1689/storyblok-mcp-server). 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.
159 Storyblok MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.