rename_branch · GitBranch MCP: Risk & Policy

WHAT IT DOES

What rename_branch does on GitBranchMCP

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

WHY IT NEEDS A POLICY

Why rename_branch needs a policy

Renaming a branch modifies existing data (the branch name record) in a reversible manner—the operation can be undone by renaming again. This fits the Write category (creates or modifies data reversibly).

From the tool's definition Tool name 'rename_branch' and description indicating it modifies branch names ('修改普通分支名称' = 'modify ordinary branch name'). This is a metadata update operation on branch records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_branch Rate-limited

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

FAQ

Questions about rename_branch

What does the rename_branch tool do? +

当用户明确要求修改普通分支名称时调用。. It is categorised as a Write tool in the GitBranchMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_branch? +

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

What risk level is rename_branch? +

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

Can I rate-limit rename_branch? +

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

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

rename_branch is provided by the GitBranch MCP server (lianggaoyuan/gitbranchmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.