Deletes a milestone.
AI agents call delete_project_milestone to permanently remove resources in Linear MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a project milestone, which cannot be undone. Deletion is irreversible and constitutes a destructive action. While the blast radius is limited to a single milestone (not organizational-level data), accidental or malicious deletion of milestones could disrupt project planning and tracking.
From the tool's definition Tool name explicitly states 'delete_project_milestone' and description confirms 'Deletes a milestone.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Deletes a milestone. It is categorised as a Destructive tool in the Linear MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Linear MCP Server MCP server in PolicyLayer and add a rule for delete_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 Linear MCP Server. Nothing to install.
delete_project_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_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_project_milestone is provided by the Linear MCP Server MCP server (sylphxai/linear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →