fetch_datasources

What fetch_datasources does on Storyblok MCP Server

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

The 'fetch' prefix strongly suggests a read-only operation that retrieves datasource configuration or metadata from Storyblok without modifying it. No language in the server description or tool name indicates content creation, deletion, or execution of external operations. The low severity reflects that unauthorized datasource reads would have minimal blast radius in a typical CMS context.

From the tool's definition Tool name 'fetch_datasources' uses 'fetch' verb which indicates data retrieval with no side effects. The tool is part of a CMS content management server where datasources are typically reference data structures (e.g., dropdown options, content sets) that are…

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

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

Questions about fetch_datasources