create_milestone_tool
AI agents use create_milestone_tool to create or update resources in MCP Gitlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Gitlab environment.
The tool appears to create a GitLab milestone, which is a reversible write operation that organizes issues and merge requests. While it modifies repository state, milestones can be edited or deleted, making it Write rather than Destructive. Confidence is 0.75 rather than higher due to empty description; if the tool had permissions to lock milestones or trigger release processes, severity might increase.
From the tool's definition Tool name indicates creation of a milestone (create_milestone_tool). No description provided to clarify exact behavior, but in GitLab context, creating a milestone is a reversible data creation operation similar to sibling tools like create_issue_tool and…
Attacks that exploit this kind of access
create_milestone_tool. It is categorised as a Write tool in the MCP Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Gitlab MCP server in PolicyLayer and add a rule for create_milestone_tool: 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 MCP Gitlab. Nothing to install.
create_milestone_tool 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_tool 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_tool. 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_tool is provided by the MCP Gitlab MCP server (mcp-gitlab-crunchtools). 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 →