get_story

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-story.md

WHAT IT DOES

What get_story does on Storyblok MCP Server

AI agents call get_story 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_story is rated Low

Despite the empty description, the tool name 'get_story' strongly indicates a read operation that retrieves story content from the Storyblok CMS without modifying or deleting data. This is consistent with the server's stated capability for 'story management' and the pattern of sibling tools that include write/destructive operations with more explicit names (create_*, copy_*, backup_*, etc.).

From the tool's definition Tool name 'get_story' combined with server description stating the tool manages content and asset handling. The 'get' prefix is a standard convention for retrieval operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_story Allowed

get_story 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_story": {}
  }
}

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_story call is checked against it from then on.

FAQ

Questions about get_story

What does the get_story tool do? +

get_story 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_story? +

Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for get_story: 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_story? +

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

Can I rate-limit get_story? +

Yes. Add a rate_limit block to the get_story 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_story completely? +

Set action: deny in the PolicyLayer policy for get_story. 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_story? +

get_story 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 →