This record as markdown: /tools/agentics-ai-code-mcp/git-branch.md
What git_branch does on Code MCP Server
AI agents use git_branch to create or update resources in Code MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Code MCP Server environment.
Why git_branch is rated Medium
Creating or switching branches are reversible write operations that alter repository state but do not permanently delete data or execute arbitrary code. Listing is read-only, but the tool's capability to create and switch branches places it in the Write category. Severity is medium because misuse could disrupt a development workflow or cause confusion, but changes are reversible via git operations.
From the tool's definition Tool description states: 'List, create, or switch branches' — the create and switch operations modify Git state by creating new branches or changing the current working branch.
Attacks that exploit this kind of access
The rule that runs git_branch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Code MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_branch, this is the rule to start with:
git_branch 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Code MCP Server, apply this rule, and every git_branch call is checked against it from then on.
Questions about git_branch
List, create, or switch branches. It is categorised as a Write tool in the Code MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Code MCP Server MCP server in PolicyLayer and add a rule for git_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 Code MCP Server. Nothing to install.
git_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_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_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_branch is provided by the Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Code MCP Server, and thousands of servers like it.
This server
Across the catalogue