update_milestone

THE RISK

Medium Risk

Why update_milestone needs a policy

This tool modifies project metadata (milestones) without deletion or financial impact. It can be reversed by updating the milestone again, placing it in Write category rather than Destructive. Severity is medium because incorrect updates could disrupt project planning timelines and confuse team coordination, but changes are not irreversible and don't directly impact production code or financial systems.

From the tool's definition update_milestone updates an existing milestone with ability to change due_date and other milestone properties, performing reversible modifications to project planning artifacts.

Documented attack patterns abuse exactly the kind of access update_milestone gives an agent:

POLICY

How to control update_milestone

PolicyLayer is an MCP gateway — it sits between your AI agents and Git MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_milestone:

policy.json

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

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.

Create a free account and register Git MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Git MCP Server tools

Destructive delete_project Delete a project from the specified platform Destructive close_merge_request close_merge_request Write close_issue Close an issue Write close_milestone Close a milestone Write create_fork create_fork Write create_issue Create a new issue in a project Write create_issue_comment Create a comment on an issue Write create_merge_request create_merge_request

All 33 Git MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_milestone

What does the update_milestone tool do? +

Update an existing milestone. due_date format: YYYY-MM-DD. It is categorised as a Write tool in the Git MCP Server 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 Git MCP Server 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 Git MCP Server. 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 Git MCP Server MCP server (yumeminami/git_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Git MCP Server tool call.

Start from Git MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →