update_release
A write tool on the Storyblok MCP server.
This record as markdown: /tools/arjuncodess-storyblok-mcp/update-release.md
What update_release does on Storyblok MCP Server
AI agents use update_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 update_release is rated Medium
The tool updates release objects, which are reversible modifications to metadata/scheduling in the CMS. This is a Write operation rather than Destructive because updates can be reverted. Severity is high because an AI agent misusing this could alter release schedules, publishing timelines, or content rollout plans affecting production environments and end users.
From the tool's definition Tool name 'update_release' indicates modification of release records in a CMS. The server context shows this is part of Storyblok CMS management where releases coordinate content publishing.
Attacks that exploit this kind of access
The rule that runs update_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 update_release, this is the rule to start with:
update_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 update_release call is checked against it from then on.
Questions about update_release
update_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 update_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.
update_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 update_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 update_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.
update_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