AI agents use git_create_branch to create or update resources in Mcp Git — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Git environment.
Creating a branch is a write operation that modifies repository state reversibly. It does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is medium because branch creation itself is low-impact, but in a CI/CD context an attacker could create branches to trigger workflows or prepare for further malicious commits.
From the tool's definition Tool name is 'git_create_branch' and description states 'Creates a new branch'. This creates a new Git branch, which modifies repository structure by adding a new ref.
Attacks that exploit this kind of access
Creates a new branch. It is categorised as a Write tool in the Mcp Git MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Git MCP server in PolicyLayer and add a rule for git_create_branch: 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 Git. Nothing to install.
git_create_branch 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 git_create_branch 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 git_create_branch. 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.
git_create_branch is provided by the Mcp Git MCP server (mcp-git). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →