Medium Risk

duplicate_workflow

duplicate_workflow

How to control duplicate_workflow ↓

What duplicate_workflow does on Storyblok MCP Server

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

Medium Risk

Why duplicate_workflow needs a policy

Duplication creates reversible changes to workflow data (a new copy), placing it in Write category. Severity is medium because workflow duplication could affect content publishing processes if misconfigured, but it remains reversible. Confidence is 0.7 due to the empty description, though the name and server context provide reasonable inference.

From the tool's definition Tool name 'duplicate_workflow' indicates copying/cloning a workflow object. The description is empty, limiting direct evidence.

Documented attack patterns abuse exactly the kind of access duplicate_workflow gives an agent:

How to control duplicate_workflow

PolicyLayer is an MCP gateway — it sits between your AI agents and Storyblok MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for duplicate_workflow:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "duplicate_workflow": {
      "limits": [
        {
          "counter": "duplicate_workflow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Storyblok MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about duplicate_workflow

What does the duplicate_workflow tool do? +

duplicate_workflow. 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 duplicate_workflow? +

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

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

Can I rate-limit duplicate_workflow? +

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

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

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

Enforce policy on every Storyblok MCP Server tool call.

Start from Storyblok MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

115 Storyblok MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.