git_branch · MCP Git Server MCP: Risk & Policy

WHAT IT DOES

What git_branch does on MCP Git Server

AI agents use git_branch to create or update resources in MCP Git Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Git Server environment.

WHY IT NEEDS A POLICY

Why git_branch needs a policy

Creating branches modifies repository metadata and structure (reversible but material change). Switching branches changes the working state. This is Write rather than Execute because the operations themselves are git primitives, not arbitrary command execution. It is not Destructive because branches can be deleted separately and these operations are reversible.

From the tool's definition Tool description states it can 'create, or switch branches' - these are write operations that modify repository state (branch creation) or change working context (branch switching). The broader server context mentions 'branch management' as a core capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_branch Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_branch": {
      "limits": [
        {
          "counter": "git_branch_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Git Server, so you can run agents against it safely.

FAQ

Questions about git_branch

What does the git_branch tool do? +

List, create, or switch branches. It is categorised as a Write tool in the MCP Git 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 git_branch? +

Register the MCP Git 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 MCP Git Server. Nothing to install.

What risk level is git_branch? +

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

Can I rate-limit git_branch? +

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.

How do I block git_branch completely? +

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.

What MCP server provides git_branch? +

git_branch is provided by the MCP Git Server MCP server (mikeybeez/mcp-git). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.