List merge requests in a GitLab project
AI agents call list_merge_requests 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 retrieves and lists existing merge requests without creating, modifying, deleting, or executing anything. It is a read-only operation that does not alter state or trigger external operations. Even if an AI agent calls it repeatedly or with various filters, the worst outcome is excessive API calls or information disclosure of already-accessible merge request metadata, which constitutes low risk.
From the tool's definition Tool name is 'list_merge_requests' and description states 'List merge requests in a GitLab project' — a pure query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List merge requests in a GitLab project. 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 list_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 MCP Server. Nothing to install.
list_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 list_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 list_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.
list_merge_requests is provided by the GitLab MCP Server MCP server (teslalord/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 →