get_access_token
A read tool on the Storyblok MCP server.
This record as markdown: /tools/arjuncodess-storyblok-mcp/get-access-token.md
What get_access_token does on Storyblok MCP Server
AI agents call get_access_token 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_access_token is rated Low
This tool retrieves authentication credentials, which is fundamentally a Read operation. However, the retrieved token could enable elevated access to perform any operation on the Storyblok space, so while the tool itself is Read-only, misuse carries medium severity risk.
From the tool's definition Tool name 'get_access_token' indicates retrieval of an authentication credential. The description is empty, but the tool's name and placement on a CMS server with content management capabilities suggest it retrieves (not creates or modifies) an access token.
Attacks that exploit this kind of access
The rule that runs get_access_token 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_access_token, this is the rule to start with:
get_access_token is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Storyblok MCP Server, apply this rule, and every get_access_token call is checked against it from then on.
Questions about get_access_token
get_access_token is a read tool on the Storyblok MCP Server MCP server. It is categorised as a Read tool in the Storyblok MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for get_access_token: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Storyblok MCP Server. Nothing to install.
get_access_token is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_access_token rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_access_token. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_access_token is provided by the Storyblok MCP Server MCP server (arjuncodess/storyblok-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Storyblok MCP Server, and thousands of servers like it.
This server
Across the catalogue