copy_stories_between_branches

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/copy-stories-between-branches.md

WHAT IT DOES

What copy_stories_between_branches does on Storyblok MCP Server

AI agents use copy_stories_between_branches 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.

RISK

Why copy_stories_between_branches is rated Medium

The operation modifies state by creating copies of stories in a different branch, which is a Write-class action (reversible data creation). High severity because bulk story copying could affect production branches or create unintended content duplication affecting site integrity. Empty description lowers confidence slightly from 0.85 to 0.8.

From the tool's definition Tool name 'copy_stories_between_branches' indicates it duplicates content across branches. Storyblok is a CMS where stories are content artifacts. Copying creates new content reversibly without deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs copy_stories_between_branches 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 copy_stories_between_branches, this is the rule to start with:

copy_stories_between_branches Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "copy_stories_between_branches": {
      "limits": [
        {
          "counter": "copy_stories_between_branches_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Storyblok MCP Server, apply this rule, and every copy_stories_between_branches call is checked against it from then on.

FAQ

Questions about copy_stories_between_branches

What does the copy_stories_between_branches tool do? +

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

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

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

Can I rate-limit copy_stories_between_branches? +

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

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

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

KEEP EXPLORING

More on Storyblok MCP Server, and thousands of servers like it.

This server

All 115 Storyblok MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →