fetch_datasource_entries

What fetch_datasource_entries does on Storyblok MCP Server

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

Based on the tool name 'fetch_datasource_entries', this is clearly a read operation that retrieves datasource entries from Storyblok CMS. The 'fetch' verb indicates data retrieval with no side effects. Even though the description is unavailable, the name provides sufficient evidence for classification as a Read operation with low severity—misuse would only expose data, not modify or delete it.

From the tool's definition Tool name 'fetch_datasource_entries' uses the verb 'fetch', which indicates retrieval of data without modification. The description is empty, but the name strongly suggests a read-only operation that queries datasource entries.

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

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

Questions about fetch_datasource_entries