List all milestones in a GitLab project
AI agents call list_milestones to retrieve information from GitLab MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation to retrieve and list existing milestones. It does not create, modify, delete, or execute any actions—it only reads data. The low severity reflects minimal blast radius if misused; at worst, an agent could enumerate milestones to gather information about project planning, which carries no destructive consequences.
From the tool's definition Tool name 'list_milestones' and description 'List all milestones in a GitLab project' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all milestones in a GitLab project. It is categorised as a Read tool in the GitLab MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for list_milestones: 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 Server. Nothing to install.
list_milestones 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_milestones 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_milestones. 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_milestones is provided by the GitLab MCP Server MCP server (therealchristhomas/gitlab-mcp-server). 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 →