New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

update_story_scheduling

A write tool on the Storyblok MCP server.

SERVERStoryblok MCP Server SOURCEarjuncodess/storyblok-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arjuncodess-storyblok-mcp/update-story-scheduling.md

What update_story_scheduling does on Storyblok MCP Server

AI agents use update_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 update_story_scheduling is rated Medium

This tool creates or modifies data (story scheduling properties) in a reversible manner—scheduling changes can be updated again or cancelled. It does not delete data (Destructive), execute arbitrary code (Execute), or commit financial transactions (Financial). The empty description limits confidence slightly, but the name and server context clearly indicate a Write operation.

From the tool's definition Tool name 'update_story_scheduling' indicates modification of story metadata (scheduling parameters). The server context shows it manages 'story management' operations in Storyblok CMS, a content management system where updating story scheduling affects…

Questions about update_story_scheduling

What does the update_story_scheduling tool do? +

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

How do I enforce a policy on update_story_scheduling? +

Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_story_scheduling? +

update_story_scheduling is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_story_scheduling? +

Yes. Add a rate_limit block to the update_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.

How do I block update_story_scheduling completely? +

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

What MCP server provides update_story_scheduling? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Storyblok MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.