list_issue_notes_tool
AI agents call list_issue_notes_tool 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 and lists existing issue notes, which is a non-destructive query operation. No side effects or data modification occurs. While the description is empty, the name and context of sibling tools (create_issue_note_tool clearly being Write) strongly indicate this is a Read operation with minimal risk.
From the tool's definition Tool name 'list_issue_notes_tool' indicates retrieval of issue notes/comments without modification. The name follows the pattern of other Read-category tools like 'compare_branches_tool' on the same server.
Attacks that exploit this kind of access
list_issue_notes_tool. 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_tool: 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_tool 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_tool 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_tool. 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_tool is provided by the MCP Gitlab MCP server (mcp-gitlab-crunchtools). 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 →