Backward-compatible alias of gitlab_update_milestone.
AI agents use gitlab_edit_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.
Updating a milestone modifies project metadata reversibly—title, description, dates, or status can be changed. This is a Write operation (modify data reversibly), not Read (no side effects), not Destructive (reversible), not Execute (not running code/commands), and not Financial.
From the tool's definition Tool is described as an alias for 'gitlab_update_milestone', which modifies milestone data. The verb 'update' and the context of a GitLab management server indicate data modification rather than retrieval or deletion.
Documented attack patterns abuse exactly the kind of access gitlab_edit_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 gitlab_edit_milestone:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_edit_milestone": {
"limits": [
{
"counter": "gitlab_edit_milestone_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}gitlab_edit_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.
Backward-compatible alias of gitlab_update_milestone. 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 gitlab_edit_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.
gitlab_edit_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 gitlab_edit_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 gitlab_edit_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.
gitlab_edit_milestone is provided by the Gitlab MCP server (mcpland/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gitlab, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
190 Gitlab tools catalogued and risk-classified — across an index of 43,000+ MCP servers.