AI agents call get_datasource to retrieve information from Storyblok MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix is a strong indicator of a read operation. Despite the empty description reducing confidence slightly, datasources in CMS systems are typically reference data or configuration that tools retrieve for content operations. No evidence suggests modification, deletion, execution, or financial impact.
From the tool's definition Tool name 'get_datasource' indicates a retrieval operation. The description is empty, limiting evidence, but the 'get_' prefix and context within a CMS content management server strongly suggests this retrieves or queries datasource configuration or data…
Documented attack patterns abuse exactly the kind of access get_datasource gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Storyblok MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_datasource:
{
"version": "1",
"default": "deny",
"tools": {
"get_datasource": {}
}
}get_datasource is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_datasource. 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_datasource: 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_datasource 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_datasource 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_datasource. 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_datasource 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.
Start from Storyblok MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
115 Storyblok MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.