debug_story_access

THE RISK

Low Risk

Why debug_story_access needs a policy

This tool retrieves or queries data about story access through fetch parameters. The verb 'debug' combined with 'access to a specific story' and 'fetch parameters' indicates a read-only diagnostic operation. There are no side effects, data modifications, deletions, or external operations triggered.

From the tool's definition Tool name 'debug_story_access' and description 'Debug access to a specific story via various fetch parameters' indicate a diagnostic/query operation that retrieves information about story access without modifying, deleting, or executing operations.

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

POLICY

How to control debug_story_access

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

policy.json

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

debug_story_access 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 bulk_delete_stories Deletes multiple stories in Storyblok. Destructive delete_access_token Delete an access token from the current Storyblok space using the Management API. Destructive delete_approval Deletes an approval from a specified Storyblok space. Destructive delete_asset Deletes an asset from Storyblok. Destructive delete_asset_folder Delete an asset folder from the current Storyblok space. Destructive delete_branch Deletes a branch (pipeline) by its ID in a Storyblok space. Destructive delete_collaborator Deletes a collaborator from a specified Storyblok space. Destructive delete_comment Deletes a comment from a discussion via the Storyblok Management API.

All 159 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

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 →

FAQ

Questions about debug_story_access

What does the debug_story_access tool do? +

Debug access to a specific story via various fetch parameters. 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 debug_story_access? +

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

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

Can I rate-limit debug_story_access? +

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

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

debug_story_access is provided by the Storyblok MCP Server MCP server (kiran1689/storyblok-mcp-server). 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 →