Low Risk

fetch_space_roles

Retrieves multiple space roles for a given space.

How to control fetch_space_roles ↓

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 — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why fetch_space_roles needs a policy

This tool only retrieves data about role configurations within a Storyblok space. It does not create, modify, delete, execute code, or move money. The blast radius of misuse is minimal—an attacker could enumerate role definitions but cannot escalate privileges or alter access controls through this retrieval alone. Hence it is classified as Read with low severity.

From the tool's definition The tool 'fetch_space_roles' has a description stating 'Retrieves multiple space roles for a given space.' The verb 'Retrieves' and the context of querying roles (not modifying them) clearly indicate a read-only operation with no side effects.

Documented attack patterns abuse exactly the kind of access fetch_space_roles gives an agent:

How to control fetch_space_roles

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 fetch_space_roles:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_space_roles": {}
  }
}

fetch_space_roles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Storyblok MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fetch_space_roles

What does the fetch_space_roles tool do? +

Retrieves multiple space roles for a given space. 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_space_roles? +

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.

What risk level is fetch_space_roles? +

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

Can I rate-limit fetch_space_roles? +

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.

How do I block fetch_space_roles completely? +

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.

What MCP server provides fetch_space_roles? +

fetch_space_roles is provided by the Storyblok MCP Server MCP server (kiran1689/storyblok-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Storyblok MCP Server tool call.

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.

159 Storyblok MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.