Low Risk

compare_story_versions

Compares two versions of a story to identify changes.

How to control compare_story_versions ↓

What compare_story_versions does on Storyblok MCP Server

AI agents call compare_story_versions 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 compare_story_versions needs a policy

This tool performs a comparison operation that queries existing story version data and outputs a diff. It has no side effects, does not create, modify, or delete content, and does not trigger external operations. It is purely informational and falls squarely within the Read category. Severity is low because reading content poses minimal risk even if misused by an AI agent.

From the tool's definition Tool description explicitly states it 'Compares two versions of a story to identify changes' — a read-only operation that retrieves and displays differences without modifying data. No mutation, deletion, or external execution is indicated.

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

How to control compare_story_versions

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

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

compare_story_versions 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 compare_story_versions

What does the compare_story_versions tool do? +

Compares two versions of a story to identify changes. 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 compare_story_versions? +

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

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

Can I rate-limit compare_story_versions? +

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

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

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