get_story_scheduling
A read tool on the Storyblok MCP server.
This record as markdown: /tools/arjuncodess-storyblok-mcp/get-story-scheduling.md
What get_story_scheduling does on Storyblok MCP Server
AI agents call get_story_scheduling 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.
Why get_story_scheduling is rated Low
The tool retrieves scheduling data for stories in Storyblok CMS. This is a read-only operation that queries existing scheduling information without creating, modifying, deleting, or executing any side effects. Even though the description is empty, the clear 'get_' prefix and context within a content management system strongly indicate this is a retrieval operation.
From the tool's definition Tool name 'get_story_scheduling' indicates retrieval of scheduling information; no description provided, but the 'get_' prefix and scheduling context within a CMS content management server suggest data querying without modification.
Attacks that exploit this kind of access
The rule that runs get_story_scheduling 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_scheduling, this is the rule to start with:
get_story_scheduling is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Storyblok MCP Server, apply this rule, and every get_story_scheduling call is checked against it from then on.
Questions about get_story_scheduling
get_story_scheduling 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.
Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for get_story_scheduling: 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.
get_story_scheduling is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_story_scheduling 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.
Set action: deny in the PolicyLayer policy for get_story_scheduling. 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.
get_story_scheduling 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.
More on Storyblok MCP Server, and thousands of servers like it.
This server
Across the catalogue