add-story-to-release · MCP Storyblok Server MCP

WHAT IT DOES

What add-story-to-release does on MCP Storyblok Server

AI agents use add-story-to-release 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 add-story-to-release needs a policy

The tool creates or modifies a relationship between existing resources (story and release) without deleting data. This is a write operation that changes state reversibly. It poses medium severity risk: an agent could associate wrong stories with releases, disrupting deployment workflows, but the action can be undone.

From the tool's definition Tool description states it 'Adds a story to an existing release' — a creation/modification operation that links a story resource to a release, reversible by removing the story from the release.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add-story-to-release Rate-limited

add-story-to-release 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": {
    "add-story-to-release": {
      "limits": [
        {
          "counter": "add-story-to-release_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 add-story-to-release

What does the add-story-to-release tool do? +

Adds a story to an existing release. 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 add-story-to-release? +

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

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

Can I rate-limit add-story-to-release? +

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

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

add-story-to-release 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.