AI agents call get_workflow_stage to retrieve information from Storyblok MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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…
Documented attack patterns abuse exactly the kind of access get_workflow_stage gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Storyblok MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_workflow_stage:
{
"version": "1",
"default": "deny",
"tools": {
"get_workflow_stage": {}
}
}get_workflow_stage is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_workflow_stage. 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.
Start from Storyblok MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
115 Storyblok MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.