List all open merge requests in the project
AI agents call list_open_merge_requests to retrieve information from GitLab MR MCP 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 information about open merge requests. It performs a read-only operation with no ability to modify, delete, or execute code. The blast radius is minimal—disclosure of MR metadata presents only informational risk. Confidence is high because the function signature and description are explicit about the read-only nature.
From the tool's definition Tool name 'list_open_merge_requests' and description 'List all open merge requests in the project' indicate a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
List all open merge requests in the project. It is categorised as a Read tool in the GitLab MR MCP MCP Server, which means it retrieves data without modifying state.
Register the GitLab MR MCP server in PolicyLayer and add a rule for list_open_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 MR MCP. Nothing to install.
list_open_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_open_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_open_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_open_merge_requests is provided by the GitLab MR MCP server (kevinlin/gitlab-mr-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 →