AI agents use branch_create to create or update resources in MCP DevTools Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP DevTools Server environment.
Creating a branch is a reversible write operation that modifies repository state but does not destroy data or execute arbitrary code. It can be undone via branch deletion. Severity is medium because misuse could create many spurious branches or interfere with development workflow, but the impact is limited to branch metadata rather than data loss or financial consequences.
From the tool's definition Tool name 'branch_create' and description 'Create a new stacked branch' indicate creation of a git branch, which modifies the repository's branch structure.
Documented attack patterns abuse exactly the kind of access branch_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP DevTools Server, and nothing reaches the server without passing your rules. This is the rule we recommend for branch_create:
{
"version": "1",
"default": "deny",
"tools": {
"branch_create": {
"limits": [
{
"counter": "branch_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}branch_create 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.
Free to start. No card required.
Create a new stacked branch. It is categorised as a Write tool in the MCP DevTools Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP DevTools Server MCP server in PolicyLayer and add a rule for branch_create: 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 MCP DevTools Server. Nothing to install.
branch_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the branch_create 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 branch_create. 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.
branch_create is provided by the MCP DevTools Server MCP server (rshade/mcp-devtools-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP DevTools 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.
79 MCP DevTools Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.