取得 Merge Request 的檔案變更（diff）
AI agents call get_merge_request_changes 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 queries and retrieves the file changes (diff) associated with a merge request. It performs a read-only operation that returns data about what has changed between branches without creating, modifying, deleting, or executing anything. No side effects or irreversible actions are possible.
From the tool's definition Tool name 'get_merge_request_changes' and description '取得 Merge Request 的檔案變更（diff）' (Get Merge Request file changes/diff) indicate retrieval of diff information without modification.
Attacks that exploit this kind of access
取得 Merge Request 的檔案變更（diff）. 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_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 MCP Server. 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 MCP Server MCP server (snowild/gitlab-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 →