AI agents call list_issue_notes to retrieve information from Gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves issue-related metadata (comments and notes) without creating, modifying, deleting, or executing anything. It has no side effects on the GitLab instance. The blast radius of misuse is minimal — an agent could enumerate comments but cannot alter project state or access unauthorized data beyond what the authenticated user already has permission to read.
From the tool's definition Fetch all comments and system notes for a GitLab issue — the verb 'Fetch' clearly indicates retrieval without modification. System notes and comments are read-only data structures.
Documented attack patterns abuse exactly the kind of access list_issue_notes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitlab, and nothing reaches the server without passing your rules. This is the rule we recommend for list_issue_notes:
{
"version": "1",
"default": "deny",
"tools": {
"list_issue_notes": {}
}
}list_issue_notes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch all comments and system notes for a GitLab issue. It is categorised as a Read tool in the Gitlab MCP Server, which means it retrieves data without modifying state.
Register the 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 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 Gitlab MCP server (yoda-digital/mcp-gitlab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 Gitlab tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 Gitlab tools catalogued and risk-classified — across an index of 42,500+ MCP servers.