Get a merge request raw difference
AI agents call get_merge_request_raw_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 raw diff (code changes) associated with a merge request. It has no side effects—it does not create, modify, delete, or execute anything. The diff is informational data used for code review purposes. Misuse by an AI agent would only expose existing code differences, presenting minimal risk.
From the tool's definition Tool name 'get_merge_request_raw_diff' and description 'Get a merge request raw difference' indicate a retrieval operation that fetches diff data without modifying state. The verb 'Get' and lack of mutation language confirm read-only semantics.
Attacks that exploit this kind of access
Get a merge request raw difference. 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_raw_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_raw_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_raw_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_raw_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_raw_diff is provided by the GitLab MCP Server MCP server (martijndormans/mcp-gitlab). 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 →