Lister les commentaires d
AI agents call list_issue_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 retrieves or queries existing issue notes/comments without modifying, deleting, or executing any operations. It has no side effects and falls squarely into the Read category. Low severity because exposure is limited to viewing comments that would typically be accessible to the user within their GitLab permissions anyway.
From the tool's definition Tool name 'list_issue_notes' with verb 'list' indicates data retrieval. Description appears truncated ('Lister les commentaires d') but 'Lister' is French for 'List', confirming read-only operation to fetch/retrieve issue comments.
Attacks that exploit this kind of access
Lister les commentaires d. 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_issue_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_issue_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_issue_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_issue_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_issue_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 →