get_merge_request_diff

Get the diff of a merge request to find valid line positions for comments.

Server GitLab MCP Server lucky-dersan/gitlab-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_merge_request_diff does on GitLab MCP Server

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.

Why get_merge_request_diff needs a policy

This tool retrieves and displays the diff (comparison) of a merge request, which is a read-only operation with no side effects. It does not modify, delete, or execute any code. The low severity reflects that accessing diff information poses minimal risk—diffs are typically visible to authorized repository members and contain no destructive or financial impact.

From the tool's definition Tool name 'get_merge_request_diff' and description 'Get the diff of a merge request' indicate a retrieval operation. The stated purpose is to 'find valid line positions for comments,' which is a read-only query of existing merge request data.

Questions about get_merge_request_diff

What does the get_merge_request_diff tool do? +

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.

How do I enforce a policy on get_merge_request_diff? +

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.

What risk level is get_merge_request_diff? +

get_merge_request_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_merge_request_diff? +

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.

How do I block get_merge_request_diff completely? +

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.

What MCP server provides get_merge_request_diff? +

get_merge_request_diff is provided by the GitLab MCP Server MCP server (lucky-dersan/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.