AI agents call delete_milestone to permanently remove resources in GitHub Repos Manager MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible delete operation on a GitHub milestone, which cannot be undone. Deletion removes the milestone and any associated metadata permanently from the repository. This qualifies as Destructive per the rubric, and carries high severity as mistaken deletion could disrupt project organization and lose tracking information for issues grouped under that milestone.
From the tool's definition Tool name 'delete_milestone' with description 'Delete a milestone' explicitly indicates irreversible deletion of a milestone resource.
Documented attack patterns abuse exactly the kind of access delete_milestone gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Repos Manager MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_milestone:
{
"version": "1",
"default": "deny",
"hide": [
"delete_milestone"
]
}delete_milestone disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a milestone. It is categorised as a Destructive tool in the GitHub Repos Manager MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GitHub Repos Manager MCP Server MCP server in PolicyLayer and add a rule for delete_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 GitHub Repos Manager MCP Server. Nothing to install.
delete_milestone is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_milestone is provided by the GitHub Repos Manager MCP Server MCP server (kurdin/github-repos-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GitHub Repos Manager 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.
84 GitHub Repos Manager MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.