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

publish_story

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/publish-story.md

What publish_story does on Storyblok MCP Server

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

Publishing a story in a CMS changes its state from draft/unpublished to published/live, affecting what content is visible to end users. This is a reversible write operation (content can be unpublished), not destructive. However, it has significant blast radius as an AI agent publishing incorrect, incomplete, or sensitive content could have business impact.

From the tool's definition Tool name 'publish_story' combined with server context showing content management operations. Publishing is a write operation that modifies content state in a CMS, making it live/public.

Questions about publish_story

What does the publish_story tool do? +

publish_story 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 publish_story? +

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

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

Can I rate-limit publish_story? +

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

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

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

Across the catalogue

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