Fetch a GitLab merge request and its contents.
AI agents call fetch_merge_request to retrieve information from GitLab MCP for Code Review 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 merge request data from GitLab—specifically its metadata and contents. There are no side effects, no code execution, no state changes, and no data modifications. While the sibling tools include write operations (add_merge_request_comment, approve_merge_request, unapprove_merge_request) and reads (fetch_commit_diff, compare_versions), this particular tool is purely informational.
From the tool's definition fetch_merge_request returns a GitLab merge request and its contents without modifying any data. The verb 'fetch' and absence of write/execute language confirm read-only retrieval.
Documented attack patterns abuse exactly the kind of access fetch_merge_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitLab MCP for Code Review, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_merge_request:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_merge_request": {}
}
}fetch_merge_request is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch a GitLab merge request and its contents. It is categorised as a Read tool in the GitLab MCP for Code Review MCP Server, which means it retrieves data without modifying state.
Register the GitLab MCP for 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 MCP for Code Review. 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 MCP for Code Review MCP server (mehmetakinn/gitlab-mcp-code-review). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GitLab MCP for Code Review, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 GitLab MCP for Code Review tools catalogued and risk-classified — across an index of 43,000+ MCP servers.