Get a list of projects with id, name, description, web_url and other useful information.
AI agents call get_projects to retrieve information from GitLab MR MCP 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 project information from GitLab without side effects. It returns static metadata (id, name, description, web_url) and does not create, modify, delete, or execute any operations. This is a standard Read operation with minimal risk—the returned data is typically already public or accessible to the authenticated user.
From the tool's definition Tool name 'get_projects' and description 'Get a list of projects with id, name, description, web_url and other useful information' indicate retrieval of project metadata without modification, deletion, or execution of code.
Attacks that exploit this kind of access
Get a list of projects with id, name, description, web_url and other useful information. It is categorised as a Read tool in the GitLab MR MCP MCP Server, which means it retrieves data without modifying state.
Register the GitLab MR MCP server in PolicyLayer and add a rule for get_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 MR MCP. Nothing to install.
get_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 get_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 get_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.
get_projects is provided by the GitLab MR MCP server (kevinlin/gitlab-mr-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 →