Get list of merge requests from GitLab project
AI agents call get-merge-requests to retrieve information from GitLab Code Review 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 returns merge request data from a GitLab project without side effects. It fits the Read category: retrieves or queries data with no side effects (similar to list, fetch, get operations). The blast radius if misused is low—an AI agent retrieving merge request lists cannot cause harm beyond potential information exposure, which is mitigated by GitLab's existing access controls.
From the tool's definition Tool retrieves a list of merge requests without modifying data. Description states 'Get list of merge requests' with no indication of mutation, deletion, or execution. This is a read-only query operation.
Attacks that exploit this kind of access
Get list of merge requests from GitLab project. It is categorised as a Read tool in the GitLab Code Review MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitLab Code Review MCP Server MCP server in PolicyLayer and add a rule for get-merge-requests: 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 Server. Nothing to install.
get-merge-requests 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-requests 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-requests. 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-requests is provided by the GitLab Code Review MCP Server MCP server (thaihoangminh/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 →