Fetch code diff for a pull request or commit
AI agents call fetch_code_diff to retrieve information from GitLab Review MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays code differences for review purposes. It has no side effects, does not modify data, does not execute code, and does not delete anything. It is purely a read operation that queries version control system data to present diffs to the user for analysis.
From the tool's definition Tool name 'fetch_code_diff' and description 'Fetch code diff for a pull request or commit' indicate retrieval of existing diff data without modification or execution of code.
Attacks that exploit this kind of access
Fetch code diff for a pull request or commit. It is categorised as a Read tool in the GitLab Review MCP MCP Server, which means it retrieves data without modifying state.
Register the GitLab Review MCP server in PolicyLayer and add a rule for fetch_code_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 GitLab Review MCP. Nothing to install.
fetch_code_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 fetch_code_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 fetch_code_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.
fetch_code_diff is provided by the GitLab Review MCP server (lininn/gitlab-review-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →