List comments on a merge request.
AI agents call list_mr_notes to retrieve information from Mcp Gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple read operation to fetch comments associated with a merge request. It has no side effects, does not modify data, does not execute code or commands, and does not delete anything. The blast radius of misuse is minimal—an AI agent could at worst retrieve comments it shouldn't have access to, a concern mitigated by underlying GitLab permissions. This is clearly a Read category tool.
From the tool's definition Tool name 'list_mr_notes' and description 'List comments on a merge request' indicate a query operation that retrieves existing data without modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
List comments on a merge request. It is categorised as a Read tool in the Mcp Gitlab MCP Server, which means it retrieves data without modifying state.
Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for list_mr_notes: 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 Mcp Gitlab. Nothing to install.
list_mr_notes 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_mr_notes 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_mr_notes. 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_mr_notes is provided by the Mcp Gitlab MCP server (wanadev/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 →