update_milestone · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What update_milestone does on Mcp Gitlab

AI agents use update_milestone 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.

WHY IT NEEDS A POLICY

Why update_milestone needs a policy

This tool updates/modifies milestone metadata (dates, descriptions, etc.) in GitLab, which is a reversible Write operation. It does not delete data (would be Destructive) or execute arbitrary code (would be Execute). The default dry-run mode provides safety guardrails. Severity is medium because incorrect milestone updates could affect project planning and team coordination, but changes can be reverted.

From the tool's definition Tool name 'update_milestone' and description 'Mettre a jour un milestone existant' (Update an existing milestone) indicates modification of existing data. The mention of 'dry_run=true' by default confirms this is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_milestone Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_milestone": {
      "limits": [
        {
          "counter": "update_milestone_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Gitlab, so you can run agents against it safely.

FAQ

Questions about update_milestone

What does the update_milestone tool do? +

Mettre a jour un milestone existant. Par defaut dry_run=true. 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.

How do I enforce a policy on update_milestone? +

Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for update_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 Mcp Gitlab. Nothing to install.

What risk level is update_milestone? +

update_milestone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_milestone? +

Yes. Add a rate_limit block to the update_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.

How do I block update_milestone completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_milestone? +

update_milestone is provided by the Mcp Gitlab MCP server (wanadev/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.