publish_release
A write tool on the Storyblok MCP server.
This record as markdown: /tools/arjuncodess-storyblok-mcp/publish-release.md
What publish_release does on Storyblok MCP Server
AI agents use publish_release 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.
Why publish_release is rated Medium
Publishing a release modifies the live state of published content in Storyblok CMS, making it a Write operation that affects production content visibility and availability. This is reversible (can unpublish or create new releases) rather than destructive. Severity is high due to potential blast radius of publishing incorrect or incomplete content to live audiences.
From the tool's definition Tool name 'publish_release' indicates publishing/releasing content in a CMS context. Sibling tools include 'add_story_to_release' and 'backup_space', establishing this as a content management server where releases represent versioned content deployments.
Attacks that exploit this kind of access
The rule that runs publish_release safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Storyblok MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For publish_release, this is the rule to start with:
publish_release 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Storyblok MCP Server, apply this rule, and every publish_release call is checked against it from then on.
Questions about publish_release
publish_release is a write tool on the Storyblok MCP Server MCP server. 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_release: 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_release 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_release 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_release. 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_release 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.
More on Storyblok MCP Server, and thousands of servers like it.
This server
Across the catalogue