get_workflow_stage
A read tool on the Storyblok MCP server.
This record as markdown: /tools/arjuncodess-storyblok-mcp/get-workflow-stage.md
What get_workflow_stage does on Storyblok MCP Server
AI agents call get_workflow_stage to retrieve information from Storyblok MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_workflow_stage is rated Low
The 'get_' prefix strongly suggests a read/query operation that retrieves workflow stage data from Storyblok CMS without side effects. No destructive, financial, or execution indicators are present in the name. The empty description reduces confidence slightly, but the naming pattern is consistent with read operations. This represents minimal risk if an AI agent invokes it, as it only retrieves information.
From the tool's definition Tool name 'get_workflow_stage' indicates a retrieval operation without a description provided. Based on naming convention and the pattern of sibling tools on the Storyblok MCP server (which includes read operations like those managing workflows), this appears…
Attacks that exploit this kind of access
The rule that runs get_workflow_stage 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 get_workflow_stage, this is the rule to start with:
get_workflow_stage is read-only, so it stays allowed. 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 get_workflow_stage call is checked against it from then on.
Questions about get_workflow_stage
get_workflow_stage is a read tool on the Storyblok MCP Server MCP server. It is categorised as a Read tool in the Storyblok MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for get_workflow_stage: 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.
get_workflow_stage is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_workflow_stage 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 get_workflow_stage. 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.
get_workflow_stage 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