Fetch a GitLab merge request and its contents.
AI agents call fetch_merge_request to retrieve information from GitLab Code Review MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves merge request data without side effects. It is a straightforward read operation that queries existing data from GitLab without creating, modifying, deleting, or executing any actions. The sibling tools (approve_merge_request, add_merge_request_comment, unapprove_merge_request) indicate write/execute capabilities exist elsewhere on the server, but this specific tool is limited to data retrieval.
From the tool's definition Tool name 'fetch_merge_request' and description 'Fetch a GitLab merge request and its contents' indicate a retrieval operation with no modification or execution capabilities.
Attacks that exploit this kind of access
Fetch a GitLab merge request and its contents. It is categorised as a Read tool in the GitLab Code Review MCP MCP Server, which means it retrieves data without modifying state.
Register the GitLab Code Review MCP server in PolicyLayer and add a rule for fetch_merge_request: 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 Code Review MCP. Nothing to install.
fetch_merge_request 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 fetch_merge_request 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 fetch_merge_request. 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.
fetch_merge_request is provided by the GitLab Code Review MCP server (lininn/gitlab-code-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 →