update-story · MCP Storyblok Server MCP: Risk & Policy

WHAT IT DOES

What update-story does on MCP Storyblok Server

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

WHY IT NEEDS A POLICY

Why update-story needs a policy

The tool creates or modifies data in a reversible manner without deleting or destroying information. While it affects CMS content, updates can typically be undone through version history or reversal operations. This is less severe than Destructive actions (like bulk-delete-stories on the same server) but more impactful than simple Read operations.

From the tool's definition Tool name is 'update-story' and description states 'Updates an existing story in Storyblok', which modifies existing content reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-story Rate-limited

update-story 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update-story": {
      "limits": [
        {
          "counter": "update-story_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Storyblok Server, so you can run agents against it safely.

FAQ

Questions about update-story

What does the update-story tool do? +

Updates an existing story in Storyblok. It is categorised as a Write tool in the MCP Storyblok 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-story? +

Register the MCP Storyblok Server MCP server in PolicyLayer and add a rule for update-story: 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 MCP Storyblok Server. Nothing to install.

What risk level is update-story? +

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

Can I rate-limit update-story? +

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

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

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