git_rename_branch · Git MCP: Risk & Policy

WHAT IT DOES

What git_rename_branch does on Git

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

WHY IT NEEDS A POLICY

Why git_rename_branch needs a policy

Renaming a branch is a reversible operation that modifies repository state (branch references) but does not destroy data or trigger external side effects. While the change affects repository structure, it can be undone by renaming the branch back. This fits the Write category (creates or modifies data reversibly).

From the tool's definition Tool name is 'git_rename_branch' and description states 'Rename an existing branch.' Renaming a branch modifies metadata and references within the repository.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_rename_branch Rate-limited

git_rename_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_rename_branch": {
      "limits": [
        {
          "counter": "git_rename_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 Git, so you can run agents against it safely.

FAQ

Questions about git_rename_branch

What does the git_rename_branch tool do? +

Rename an existing branch. It is categorised as a Write tool in the Git 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_rename_branch? +

Register the Git MCP server in PolicyLayer and add a rule for git_rename_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 Git. Nothing to install.

What risk level is git_rename_branch? +

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

Can I rate-limit git_rename_branch? +

Yes. Add a rate_limit block to the git_rename_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_rename_branch completely? +

Set action: deny in the PolicyLayer policy for git_rename_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_rename_branch? +

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