AI agents use close_milestone to create or update resources in Git MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git MCP Server environment.
Closing a milestone modifies the state of a project management artifact but does not delete data or cause irreversible harm. The action is reversible (milestones can typically be reopened), and the blast radius is limited to workflow/project tracking impact rather than data loss or financial consequence.
From the tool's definition Tool name 'close_milestone' and description 'Close a milestone' indicate a state change operation on a milestone object. This is a reversible modification—the milestone can be reopened.
Documented attack patterns abuse exactly the kind of access close_milestone gives an agent:
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 close_milestone:
{
"version": "1",
"default": "deny",
"tools": {
"close_milestone": {
"limits": [
{
"counter": "close_milestone_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}close_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.
Close a milestone. 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.
Register the Git MCP Server MCP server in PolicyLayer and add a rule for close_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.
close_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 close_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 close_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.
close_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.
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.
Free to start. No card required.
33 Git MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.