Scan git diff between two branches for code quality issues. Ideal for PR/MR review — only analyzes changed files and lines.
AI agents call scan_diff to retrieve information from Open Code Review without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only analysis tool. It retrieves and examines git diff data to detect potential defects, but produces only informational output (code review findings). There are no side effects, no data modifications, no command execution, and no destructive operations.
From the tool's definition Tool 'scan_diff' analyzes git differences and scans for code quality issues without modifying any code or executing external operations.
Documented attack patterns abuse exactly the kind of access scan_diff gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Open Code Review, and nothing reaches the server without passing your rules. This is the rule we recommend for scan_diff:
{
"version": "1",
"default": "deny",
"tools": {
"scan_diff": {}
}
}scan_diff is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Scan git diff between two branches for code quality issues. Ideal for PR/MR review — only analyzes changed files and lines. It is categorised as a Read tool in the Open Code Review MCP Server, which means it retrieves data without modifying state.
Register the Open Code Review MCP server in PolicyLayer and add a rule for scan_diff: 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 Open Code Review. Nothing to install.
scan_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the scan_diff 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 scan_diff. 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.
scan_diff is provided by the Open Code Review MCP server (raye-deng/open-code-review). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Open Code Review, 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.
4 Open Code Review tools catalogued and risk-classified — across an index of 43,000+ MCP servers.