list_project_vulnerabilities
List vulnerabilities for a project with optional state, severity, and report type filters (GraphQL-backed, cursor pagination)
This record as markdown: /tools/io-github-zereight-gitlab-mcp/list-project-vulnerabilities.md
What list_project_vulnerabilities does on Gitlab Mcp
AI agents call list_project_vulnerabilities to retrieve information from Gitlab Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_project_vulnerabilities is rated Low
This tool retrieves vulnerability data for a project using GraphQL-backed queries with optional filters and pagination. It performs no side effects, creates no resources, executes no code, modifies no data, and has no destructive or financial impact. It is a straightforward read operation on project metadata.
From the tool's definition Tool name and description indicate a 'list' operation that 'List vulnerabilities for a project' with filtering options.
Attacks that exploit this kind of access
The rule that runs list_project_vulnerabilities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_project_vulnerabilities, this is the rule to start with:
list_project_vulnerabilities is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every list_project_vulnerabilities call is checked against it from then on.
Questions about list_project_vulnerabilities
List vulnerabilities for a project with optional state, severity, and report type filters (GraphQL-backed, cursor pagination). It is categorised as a Read tool in the Gitlab Mcp MCP Server, which means it retrieves data without modifying state.
Register the Gitlab MCP server in PolicyLayer and add a rule for list_project_vulnerabilities: 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 Mcp. Nothing to install.
list_project_vulnerabilities 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_vulnerabilities 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_vulnerabilities. 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_vulnerabilities is provided by the Gitlab MCP server (@zereight/mcp-gitlab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gitlab, and thousands of servers like it.
This server
Across the catalogue