git_checkout_branch · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What git_checkout_branch does on LocalAnt

AI agents invoke git_checkout_branch to trigger actions in LocalAnt. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why git_checkout_branch needs a policy

Checking out a branch switches the working tree and HEAD pointer to a different branch, which modifies the state of the local repository (working directory, staged files, etc.). While not irreversibly destructive in most cases, it is an active operation that changes filesystem state and can overwrite uncommitted local changes, making it Execute-level with medium severity.

From the tool's definition git_checkout_branch — 'Checkout an existing branch'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_checkout_branch Rate-limited

git_checkout_branch stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_branch": {
      "limits": [
        {
          "counter": "git_checkout_branch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about git_checkout_branch

What does the git_checkout_branch tool do? +

Checkout an existing branch. It is categorised as a Execute tool in the LocalAnt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on git_checkout_branch? +

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

What risk level is git_checkout_branch? +

git_checkout_branch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit git_checkout_branch? +

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

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

git_checkout_branch is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.