List issues for a specific project (not group). Filter by state, labels, milestone, assignee, iteration.
AI agents call list_project_issues 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 queries existing issue data with no side effects. It does not create, modify, delete, or execute any operations—it only lists/filters issues based on provided criteria, which is characteristic of a Read operation. The low severity reflects minimal blast radius if misused by an AI agent, as it only exposes existing issue information.
From the tool's definition Tool name 'list_project_issues' and description 'List issues for a specific project' indicate retrieval of data without modification. Filtering parameters (state, labels, milestone, assignee, iteration) are all read-only query operations.
Attacks that exploit this kind of access
List issues for a specific project (not group). Filter by state, labels, milestone, assignee, iteration. 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_project_issues: 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_project_issues 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_project_issues 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_project_issues. 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_project_issues 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 →