get_story_versions

What get_story_versions does on Storyblok MCP Server

AI agents call get_story_versions to retrieve information from Storyblok MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_story_versions is rated Low

The tool name strongly implies fetching/retrieving story version data (Read operation). The empty description reduces confidence slightly, but the naming convention and CMS context support a read-only classification. No side effects, destructive operations, or financial impact are evident. Severity is low because retrieving version information poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'get_story_versions' indicates a retrieval operation; the 'get_' prefix is a standard convention for read-only queries. The Storyblok CMS context suggests this retrieves version history of a story without modifying or deleting data.

The rule that runs get_story_versions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Storyblok MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_story_versions, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_story_versions": {}
  }
}

Questions about get_story_versions