fetch_space_roles
A read tool on the Storyblok MCP server.
This record as markdown: /tools/arjuncodess-storyblok-mcp/fetch-space-roles.md
What fetch_space_roles does on Storyblok MCP Server
AI agents call fetch_space_roles 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 fetch_space_roles is rated Low
This tool retrieves role data from a Storyblok CMS space, consistent with Read category operations (fetch, list, get). No side effects, modifications, or destructive actions are implied. Severity is low because roles data is typically non-sensitive metadata used for access control purposes, and misuse would primarily result in information disclosure rather than system compromise or data loss.
From the tool's definition Tool name 'fetch_space_roles' indicates retrieval of role information from a Storyblok space. The verb 'fetch' denotes a read operation with no data modification. Description is empty, lowering confidence slightly.
Attacks that exploit this kind of access
The rule that runs fetch_space_roles 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_space_roles, this is the rule to start with:
fetch_space_roles 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 fetch_space_roles call is checked against it from then on.
Questions about fetch_space_roles
fetch_space_roles 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 fetch_space_roles: 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.
fetch_space_roles 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 fetch_space_roles 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 fetch_space_roles. 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.
fetch_space_roles 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