fetch_workflow_stages

A read tool on the Storyblok MCP server.

SERVERStoryblok MCP Server SOURCEarjuncodess/storyblok-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arjuncodess-storyblok-mcp/fetch-workflow-stages.md

WHAT IT DOES

What fetch_workflow_stages does on Storyblok MCP Server

AI agents call fetch_workflow_stages 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.

RISK

Why fetch_workflow_stages is rated Low

The 'fetch' prefix strongly suggests this tool retrieves workflow stage information from Storyblok CMS without modifying, deleting, or executing external operations. Even without a description, the semantic meaning of 'fetch' in the context of a CMS management server indicates a data retrieval operation with no side effects.

From the tool's definition Tool name 'fetch_workflow_stages' uses the verb 'fetch', which indicates retrieval of data. The tool description is empty, limiting direct confirmation, but the naming convention aligns with read-only query operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fetch_workflow_stages 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 fetch_workflow_stages, this is the rule to start with:

fetch_workflow_stages Allowed

fetch_workflow_stages is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_workflow_stages": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Storyblok MCP Server, apply this rule, and every fetch_workflow_stages call is checked against it from then on.

FAQ

Questions about fetch_workflow_stages

What does the fetch_workflow_stages tool do? +

fetch_workflow_stages 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.

How do I enforce a policy on fetch_workflow_stages? +

Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for fetch_workflow_stages: 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.

What risk level is fetch_workflow_stages? +

fetch_workflow_stages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fetch_workflow_stages? +

Yes. Add a rate_limit block to the fetch_workflow_stages 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.

How do I block fetch_workflow_stages completely? +

Set action: deny in the PolicyLayer policy for fetch_workflow_stages. 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.

What MCP server provides fetch_workflow_stages? +

fetch_workflow_stages 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.

KEEP EXPLORING

More on Storyblok MCP Server, and thousands of servers like it.

This server

All 115 Storyblok MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →