get_datasource_entry

A read tool on the Storyblok MCP server.

SERVERStoryblok MCP Server SOURCEarjuncodess/storyblok-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arjuncodess-storyblok-mcp/get-datasource-entry.md

WHAT IT DOES

What get_datasource_entry does on Storyblok MCP Server

AI agents call get_datasource_entry 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.

RISK

Why get_datasource_entry is rated Low

The 'get_' prefix strongly indicates a read-only operation that retrieves data from a datasource. While the empty description reduces confidence slightly, the tool naming convention and context within a CMS content management server support classification as a Read operation with low severity. No destructive, financial, or code execution capabilities are implied.

From the tool's definition Tool name 'get_datasource_entry' with 'get_' prefix indicates a retrieval operation. No description provided, but naming convention suggests querying a datasource entry from Storyblok CMS without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_datasource_entry Allowed

get_datasource_entry is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Storyblok MCP Server, apply this rule, and every get_datasource_entry call is checked against it from then on.

FAQ

Questions about get_datasource_entry

What does the get_datasource_entry tool do? +

get_datasource_entry 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.

How do I enforce a policy on get_datasource_entry? +

Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for get_datasource_entry: 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.

What risk level is get_datasource_entry? +

get_datasource_entry is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_datasource_entry? +

Yes. Add a rate_limit block to the get_datasource_entry 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.

How do I block get_datasource_entry completely? +

Set action: deny in the PolicyLayer policy for get_datasource_entry. 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.

What MCP server provides get_datasource_entry? +

get_datasource_entry 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.

KEEP EXPLORING

More on Storyblok MCP Server, and thousands of servers like it.

This server

All 115 Storyblok MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →