close_project_milestone · Mcp Gitlab MCP: Risk & Policy

WHAT IT DOES

What close_project_milestone does on Mcp Gitlab

AI agents use close_project_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 close_project_milestone needs a policy

Closing a milestone is a reversible state change that modifies project metadata without destructively removing data or executing arbitrary code. While it could disrupt project tracking workflows, the dry-run safety and reversible nature place it in Write rather than Execute or Destructive. Medium severity reflects potential workflow disruption but limited blast radius in a software development context.

From the tool's definition Tool description states "Close a project-level milestone" which modifies the state of a milestone resource. The dry_run=true default indicates the action is reversible (milestones can be reopened), and closing is a state modification rather than deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_project_milestone Rate-limited

close_project_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": {
    "close_project_milestone": {
      "limits": [
        {
          "counter": "close_project_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 close_project_milestone

What does the close_project_milestone tool do? +

Close a project-level milestone. dry_run=true by default. 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 close_project_milestone? +

Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for close_project_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 close_project_milestone? +

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

Can I rate-limit close_project_milestone? +

Yes. Add a rate_limit block to the close_project_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 close_project_milestone completely? +

Set action: deny in the PolicyLayer policy for close_project_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 close_project_milestone? +

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