git_bisect · Git MCP: Risk & Policy

WHAT IT DOES

What git_bisect does on Git

AI agents invoke git_bisect to trigger actions in Git. 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_bisect needs a policy

git_bisect is an Execute risk because it automates sequential operations (checkout commits, run tests, mark commits as good/bad) whose side effects depend on the repository state and test outcomes. While not destructive itself, bisect can trigger arbitrary test scripts and leave the repository in intermediate states.

From the tool's definition Tool runs 'bisect workflows for bug isolation' — a complex Git operation that executes automated testing and state transitions across commits without reversibility constraints. The description explicitly states 'run', indicating active execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_bisect Rate-limited

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

FAQ

Questions about git_bisect

What does the git_bisect tool do? +

Run bisect workflows for bug isolation. It is categorised as a Execute tool in the Git 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_bisect? +

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

What risk level is git_bisect? +

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

Can I rate-limit git_bisect? +

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

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

git_bisect is provided by the Git MCP server (selfagency/git-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.