create_workflow_stage_change
A write tool on the Storyblok MCP server.
This record as markdown: /tools/arjuncodess-storyblok-mcp/create-workflow-stage-change.md
What create_workflow_stage_change does on Storyblok MCP Server
AI agents use create_workflow_stage_change 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 create_workflow_stage_change is rated Medium
The tool creates a new workflow stage change, which is a reversible modification to workflow metadata or state within the CMS. This is categorized as Write rather than Execute because it appears to create/modify data objects rather than trigger external operations or execute arbitrary code.
From the tool's definition Tool name 'create_workflow_stage_change' indicates creation of a workflow stage change object. The Storyblok context (CMS content management) suggests this modifies workflow state. No description provided to confirm exact behavior.
Attacks that exploit this kind of access
The rule that runs create_workflow_stage_change 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 create_workflow_stage_change, this is the rule to start with:
create_workflow_stage_change 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 create_workflow_stage_change call is checked against it from then on.
Questions about create_workflow_stage_change
create_workflow_stage_change 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 create_workflow_stage_change: 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.
create_workflow_stage_change 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_workflow_stage_change 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_workflow_stage_change. 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_workflow_stage_change 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