get_branch

What get_branch does on Storyblok MCP Server

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

The 'get_branch' tool retrieves or queries branch information from Storyblok CMS without modifying, executing, or deleting anything. It aligns with standard Read operations (get, fetch) in the MCP classification scheme. Confidence is slightly reduced (0.85 vs. 0.95) due to the empty description, but the name and context are clear enough to justify high confidence in the Read category.

From the tool's definition Tool name 'get_branch' indicates a retrieval operation. The empty description is uninformative, but the verb 'get' and the context of a CMS server managing branches (a read-only versioning feature) strongly suggest data retrieval with no side effects.

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

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

Questions about get_branch