Binary search for the commit that introduced a bug. Returns structured data with action taken, current commit, remaining steps estimate, and result.
AI agents invoke bisect to trigger actions in Lint. 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.
The tool runs git bisect operations which execute external VCS commands and traverse commit history. While it is primarily a read/search operation conceptually, it actively executes git commands that change repository HEAD state (checking out commits), making it Execute. Misuse could leave a repository in a detached HEAD or bisect state, but effects are generally reversible, placing severity at medium.
From the tool's definition 'Binary search for the commit that introduced a bug' — triggers git bisect operations (run, start, good, bad, reset) against a repository, executing VCS commands whose effects depend on arguments
Documented attack patterns abuse exactly the kind of access bisect gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lint, and nothing reaches the server without passing your rules. This is the rule we recommend for bisect:
{
"version": "1",
"default": "deny",
"tools": {
"bisect": {
"limits": [
{
"counter": "bisect_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Binary search for the commit that introduced a bug. Returns structured data with action taken, current commit, remaining steps estimate, and result. It is categorised as a Execute tool in the Lint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Lint MCP server in PolicyLayer and add a rule for 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 Lint. Nothing to install.
bisect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
bisect is provided by the Lint MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lint, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Lint tools catalogued and risk-classified — across an index of 43,000+ MCP servers.