git-checkout · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What git-checkout does on GitHub MCP Server

AI agents invoke git-checkout to trigger actions in GitHub MCP Server. 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 needs a policy

git-checkout changes the working tree state by switching branches or creating new ones. This is an active operation that modifies the current working directory state and HEAD pointer. It can overwrite uncommitted local changes and affect the repository's working state, making it an Execute-level action rather than a simple Read or Write.

From the tool's definition Switches to a branch or creates and switches to a new branch

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git-checkout Rate-limited

git-checkout 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": {
      "limits": [
        {
          "counter": "git-checkout_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 GitHub MCP Server, so you can run agents against it safely.

FAQ

Questions about git-checkout

What does the git-checkout tool do? +

Switches to a branch or creates and switches to a new branch. It is categorised as a Execute tool in the GitHub MCP Server 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? +

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

What risk level is git-checkout? +

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

Can I rate-limit git-checkout? +

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

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

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