git_checkout_new_branch · Coding MCP Server MCP

WHAT IT DOES

What git_checkout_new_branch does on Coding MCP Server

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

WHY IT NEEDS A POLICY

Why git_checkout_new_branch needs a policy

This tool creates a new git branch and switches to it. Creating a branch is a reversible write operation — it does not delete data or execute arbitrary code. Misuse could disrupt repository state (e.g., unexpected branch proliferation or switching context mid-workflow), but effects are reversible by deleting the branch or checking out another.

From the tool's definition Create and checkout a new git branch

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_checkout_new_branch Rate-limited

git_checkout_new_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_checkout_new_branch": {
      "limits": [
        {
          "counter": "git_checkout_new_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 Coding MCP Server, so you can run agents against it safely.

FAQ

Questions about git_checkout_new_branch

What does the git_checkout_new_branch tool do? +

Create and checkout a new git branch. It is categorised as a Write tool in the Coding MCP 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_checkout_new_branch? +

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

What risk level is git_checkout_new_branch? +

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

Can I rate-limit git_checkout_new_branch? +

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

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

git_checkout_new_branch is provided by the Coding MCP Server MCP server (kieutrongthien/coding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.