Get project milestones.
AI agents call get_project_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 retrieves or lists project milestones—a pure query operation that returns data without creating, modifying, deleting, or executing any actions. It has minimal blast radius if misused by an AI agent, as it only exposes read access to milestone metadata. The 'get' verb and absence of any modification language clearly categorize it as Read.
From the tool's definition Tool name 'get_project_milestones' and description 'Get project milestones' indicate a retrieval operation with the verb 'get', which queries existing milestone data without modification or side effects.
Attacks that exploit this kind of access
Get project milestones. 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 get_project_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.
get_project_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 get_project_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 get_project_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.
get_project_milestones is provided by the GitLab MCP Server MCP server (skmprb/gitlab-clone-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 →