translate_story
A write tool on the Storyblok MCP server.
This record as markdown: /tools/arjuncodess-storyblok-mcp/translate-story.md
What translate_story does on Storyblok MCP Server
AI agents use translate_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.
Why translate_story is rated Medium
Based on the tool name and server context, 'translate_story' likely creates or modifies translated content within Storyblok CMS. Translation operations typically write new language variants of existing stories. The description is empty, which lowers confidence. Severity is high because mistranslating or overwriting story content in a CMS can have significant content impact across a site.
From the tool's definition Tool name 'translate_story' and server context of Storyblok CMS story management; description is empty.
Attacks that exploit this kind of access
The rule that runs translate_story 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 translate_story, this is the rule to start with:
translate_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Storyblok MCP Server, apply this rule, and every translate_story call is checked against it from then on.
Questions about translate_story
translate_story 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 translate_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.
translate_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 translate_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 translate_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.
translate_story 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