Get merge request changes (GitLab compatibility alias)
AI agents call get_merge_request_changes 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 fetches and displays merge request changes/diffs without modifying any data. It has no side effects and no capability to alter code, delete resources, or trigger external operations. The 'get' verb and context within a code review system confirm it is a read-only query operation with minimal blast radius.
From the tool's definition Tool name 'get_merge_request_changes' uses 'get' prefix indicating retrieval. Description states it retrieves merge request changes. Sibling tools like 'fetch_code_diff', 'fetch_pull_request', and 'get_project_info' are clearly read-only retrieval operations.
Attacks that exploit this kind of access
Get merge request changes (GitLab compatibility alias). 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 get_merge_request_changes: 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.
get_merge_request_changes 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_changes 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_changes. 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_changes 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 →