AI agents use create_milestone to create or update resources in Gitlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab environment.
This tool creates new data (a milestone) in GitLab, which is reversible (milestones can be deleted or modified). It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. It fits squarely in the Write category. Severity is medium because creating milestones could be misused to clutter projects or disrupt planning workflows, but the impact is limited in scope and reversible.
From the tool's definition Tool name is 'create_milestone' and description states 'Create a new milestone in a GitLab project' — this is a creation operation that modifies project state by adding a new milestone.
Documented attack patterns abuse exactly the kind of access create_milestone gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gitlab, and nothing reaches the server without passing your rules. This is the rule we recommend for create_milestone:
{
"version": "1",
"default": "deny",
"tools": {
"create_milestone": {
"limits": [
{
"counter": "create_milestone_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_milestone stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new milestone in a GitLab project. It is categorised as a Write tool in the Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitlab MCP server in PolicyLayer and add a rule for create_milestone: 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. Nothing to install.
create_milestone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_milestone 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 create_milestone. 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.
create_milestone is provided by the Gitlab MCP server (yoda-digital/mcp-gitlab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 Gitlab tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 Gitlab tools catalogued and risk-classified — across an index of 42,500+ MCP servers.