create_story_scheduling
A write tool on the Storyblok MCP server.
This record as markdown: /tools/arjuncodess-storyblok-mcp/create-story-scheduling.md
What create_story_scheduling does on Storyblok MCP Server
AI agents use create_story_scheduling to create or update resources in Storyblok MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Storyblok MCP Server environment.
Why create_story_scheduling is rated Medium
This tool creates or modifies scheduling configurations for stories, which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), move money (would be Financial), or merely retrieve data (would be Read).
From the tool's definition Tool name 'create_story_scheduling' indicates creation of scheduling configurations for stories in a CMS. Sibling tools like 'create_branch', 'create_asset_folder', and 'add_story_to_release' are all Write operations that create or modify CMS content.
Attacks that exploit this kind of access
The rule that runs create_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 create_story_scheduling, this is the rule to start with:
create_story_scheduling stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_story_scheduling call is checked against it from then on.
Questions about create_story_scheduling
create_story_scheduling is a write tool on the Storyblok MCP Server MCP server. It is categorised as a Write tool in the Storyblok MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_story_scheduling is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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