Get information about a specific GitLab merge request
AI agents call get_merge_request 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 retrieves and queries merge request metadata and details from GitLab. It has no capability to modify, delete, or execute operations. The verb 'Get' and the informational nature of the operation place it squarely in the Read category. Severity is low because the blast radius of misuse is minimal—an agent could only access existing information that may already be visible to authenticated users.
From the tool's definition Tool name is 'get_merge_request' and description states 'Get information about a specific GitLab merge request' - both indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get information about a specific GitLab merge request. 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: 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 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 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. 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 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 →