fetch_story_schedulings

What fetch_story_schedulings does on Storyblok MCP Server

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

The 'fetch' verb in the tool name is a standard pattern for retrieval operations that query and return data with no side effects. Even though the description is empty, the naming convention and sibling tools context (which include explicit write/execute/destructive operations like 'copy_stories_between_branches', 'create_branch', 'backup_space') clearly position this as a simple data retrieval function.

From the tool's definition Tool name 'fetch_story_schedulings' with 'fetch' prefix indicates data retrieval operation. The Storyblok CMS context shows this queries scheduling information for stories without modifying or executing operations.

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

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

Questions about fetch_story_schedulings