AI agents invoke create_branch_deployment to trigger actions in Storyblok MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The name implies triggering a deployment operation (deploying a branch), which is an external operation/execution rather than a simple write. However, the description is empty, so confidence is low. Based on naming conventions and sibling context, this likely triggers a deployment process, placing it in Execute category. Severity is medium as deployments can affect live content environments.
From the tool's definition Tool name 'create_branch_deployment' and empty description; sibling tools include 'create_branch' and 'compare_branches' suggesting branch/deployment management in Storyblok CMS
Documented attack patterns abuse exactly the kind of access create_branch_deployment gives an agent:
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 create_branch_deployment:
{
"version": "1",
"default": "deny",
"tools": {
"create_branch_deployment": {
"limits": [
{
"counter": "create_branch_deployment_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}create_branch_deployment stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_branch_deployment. It is categorised as a Execute tool in the Storyblok MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Storyblok MCP Server MCP server in PolicyLayer and add a rule for create_branch_deployment: 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_branch_deployment is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_branch_deployment 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_branch_deployment. 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_branch_deployment 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.
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.