Medium Risk

update_space

Updates an existing Storyblok space via the Management API.

How to control update_space ↓

What update_space does on Storyblok MCP Server

AI agents use update_space to create or update resources in Storyblok MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Storyblok MCP Server environment.

Medium Risk

Why update_space needs a policy

The tool modifies an existing space configuration in Storyblok, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move money, so it falls under Write category.

From the tool's definition Tool name is 'update_space' and description states it 'Updates an existing Storyblok space via the Management API', indicating creation or modification of data.

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

How to control update_space

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_space": {
      "limits": [
        {
          "counter": "update_space_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_space stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about update_space

What does the update_space tool do? +

Updates an existing Storyblok space via the Management API. It is categorised as a Write tool in the Storyblok MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_space? +

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

update_space is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_space? +

Yes. Add a rate_limit block to the update_space 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 update_space completely? +

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

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