get_story_by_slug

THE RISK

Low Risk

Why get_story_by_slug needs a policy

The tool retrieves data (a story record) based on a slug parameter. This is a read-only operation with no side effects—it does not create, modify, delete, or execute code. The 'get_' prefix is characteristic of Read category tools. Even though the description is empty, the tool name provides sufficient evidence of its purpose as a retrieval operation.

From the tool's definition Tool name 'get_story_by_slug' indicates retrieval of a story by its identifier. No description provided, but the naming pattern and context within a CMS server (Storyblok) strongly suggests a query/fetch operation that retrieves existing content without…

Documented attack patterns abuse exactly the kind of access get_story_by_slug gives an agent:

POLICY

How to control get_story_by_slug

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_story_by_slug:

policy.json

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

get_story_by_slug is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Storyblok MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Storyblok MCP Server tools

Destructive delete_access_token delete_access_token Destructive delete_asset delete_asset Destructive delete_asset_folder delete_asset_folder Destructive delete_branch delete_branch Destructive delete_component delete_component Destructive delete_component_folder delete_component_folder Destructive delete_datasource delete_datasource Destructive delete_datasource_entry delete_datasource_entry

All 115 Storyblok MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

Roll out MCP under one policy → Per-person scoped tokens, one central policy, and full audit across every server your team connects.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about get_story_by_slug

What does the get_story_by_slug tool do? +

get_story_by_slug. 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_by_slug? +

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

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

Can I rate-limit get_story_by_slug? +

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

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

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

Enforce policy on every Storyblok MCP Server tool call.

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.

CHECK YOUR STACK →