Get the diff of a merge request to find valid line positions for comments.
AI agents call get_merge_request_diff to retrieve information from GitLab 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 the diff (changes) of a merge request. It has no side effects—it does not create, modify, delete, or execute anything. It is purely informational, used to inspect code changes before commenting. The low severity reflects minimal blast radius: an attacker could view diffs but cannot modify code, merge branches, or trigger deployments.
From the tool's definition Tool name 'get_merge_request_diff' and description 'Get the diff of a merge request' indicate a retrieval operation with no modification capability. The stated purpose is to 'find valid line positions for comments,' a read-only use case.
Documented attack patterns abuse exactly the kind of access get_merge_request_diff gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitLab MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_merge_request_diff:
{
"version": "1",
"default": "deny",
"tools": {
"get_merge_request_diff": {}
}
}get_merge_request_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.
Get the diff of a merge request to find valid line positions for comments. It is categorised as a Read tool in the GitLab MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for get_merge_request_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 MCP Server. Nothing to install.
get_merge_request_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 get_merge_request_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 get_merge_request_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.
get_merge_request_diff is provided by the GitLab MCP Server MCP server (radostkali/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GitLab MCP Server, 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.
8 GitLab MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.