get_story_by_slug

What get_story_by_slug does on Storyblok MCP Server

AI agents call get_story_by_slug 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_by_slug is rated Low

The tool retrieves data (a story record) based on a slug parameter. This is a read-only operation with no side effects—it does not create, modify, delete, or execute code. The 'get_' prefix is characteristic of Read category tools. Even though the description is empty, the tool name provides sufficient evidence of its purpose as a retrieval operation.

From the tool's definition Tool name 'get_story_by_slug' indicates retrieval of a story by its identifier. No description provided, but the naming pattern and context within a CMS server (Storyblok) strongly suggests a query/fetch operation that retrieves existing content without…

The rule that runs get_story_by_slug 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_by_slug, this is the rule to start with:

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

Questions about get_story_by_slug