Get diffs for a specific merge request from GitLab project
AI agents call get-merge-request-diffs to retrieve information from GitLab Code Review MCP Server 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 changes (diffs) from an existing merge request. It performs no modifications, deletions, or executions. The blast radius of misuse is minimal—an agent could only view code differences, which poses no security risk. This is a straightforward Read category tool used for inspection during code review workflows.
From the tool's definition Tool name 'get-merge-request-diffs' and description 'Get diffs for a specific merge request' clearly indicate a retrieval operation.
Attacks that exploit this kind of access
Get diffs for a specific merge request from GitLab project. It is categorised as a Read tool in the GitLab Code Review MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitLab Code Review MCP Server MCP server in PolicyLayer and add a rule for get-merge-request-diffs: 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 Code Review MCP Server. Nothing to install.
get-merge-request-diffs 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 get-merge-request-diffs 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 get-merge-request-diffs. 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.
get-merge-request-diffs is provided by the GitLab Code Review MCP Server MCP server (thaihoangminh/code-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 →