fetch_access_tokens

What fetch_access_tokens does on Storyblok MCP Server

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

The tool retrieves access token data from Storyblok, which constitutes a Read operation—querying information without side effects. However, the empty description reduces confidence slightly, as we cannot confirm the exact scope or whether the tokens are sensitive in nature. Access tokens themselves are credentials, but fetching them to display to an authorized user is a read operation.

From the tool's definition Tool name 'fetch_access_tokens' indicates retrieval of existing access tokens without modification. No description provided, but 'fetch' is a retrieval verb consistent with Read operations.

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

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

Questions about fetch_access_tokens