retrieve_multiple_story_schedules

THE RISK

Low Risk

Why retrieve_multiple_story_schedules needs a policy

This tool fetches scheduling metadata for stories within Storyblok, which is a read-only operation that queries existing data without side effects. No data is created, modified, deleted, or executed. The low severity reflects minimal blast radius—retrieving schedule information poses no risk of unintended data loss, financial impact, or system compromise.

From the tool's definition Tool name 'retrieve_multiple_story_schedules' and description 'Retrieves multiple story scheduling entries' indicate a data retrieval operation with no modification, deletion, or execution of external processes.

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

POLICY

How to control retrieve_multiple_story_schedules

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

policy.json

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

retrieve_multiple_story_schedules 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 retrieve_multiple_story_schedules

What does the retrieve_multiple_story_schedules tool do? +

Retrieves multiple story scheduling entries in a Storyblok space via the Management API. 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 retrieve_multiple_story_schedules? +

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

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

Can I rate-limit retrieve_multiple_story_schedules? +

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

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

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