git_branch · Context MCP: Risk & Policy

WHAT IT DOES

What git_branch does on Context

AI agents invoke git_branch to trigger actions in Context. 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_branch needs a policy

While listing branches is a Read operation, creating and checking out branches modifies the git repository state (creating new refs, changing HEAD). These are external operations with side effects. The most severe applicable category is Execute, since checking out a branch can change working directory state and HEAD pointer, affecting ongoing work.

From the tool's definition 'List, create, or checkout branches' — creating and checking out branches are operations that modify repository state and trigger external git operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_branch Rate-limited

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

FAQ

Questions about git_branch

What does the git_branch tool do? +

List, create, or checkout branches. It is categorised as a Execute tool in the Context 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_branch? +

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

What risk level is git_branch? +

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

Can I rate-limit git_branch? +

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

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

git_branch is provided by the Context MCP server (vibhasdutta/context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.