list_projects
AI agents call list_projects to retrieve information from GitLab MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
'list_projects' retrieves project information from GitLab. No creation, modification, deletion, code execution, or financial impact is possible. This is a standard Read operation with minimal blast radius—an agent querying projects poses no direct risk. The empty description slightly lowers confidence, but the unambiguous name and context (GitLab REST API) strongly support Read classification.
From the tool's definition Tool name 'list_projects' is a retrieval operation with no side effects. Description is empty, but the name and typical REST API convention clearly indicate this lists/queries existing projects without modification.
Attacks that exploit this kind of access
list_projects. 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_projects: 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_projects 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_projects 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_projects. 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_projects is provided by the GitLab MCP server (shahabmosavi/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 →