New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

linear_delete_milestone

A destructive tool on the All MCP server.

SERVERAllmcp SOURCEPerception-Dynamics-Inc/allmcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/allmcp/linear-delete-milestone.md

What linear_delete_milestone does on Allmcp

AI agents call linear_delete_milestone to permanently remove resources in Allmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why linear_delete_milestone is rated Critical

The 'delete' verb is unambiguous—this tool removes data that cannot be undone. Deletion of milestones in a project management system is destructive and potentially high-impact if triggered incorrectly by an AI agent, affecting team planning and historical records. Destructive category takes precedence over Read/Write/Execute per the severity hierarchy.

From the tool's definition Tool name is 'linear_delete_milestone' which explicitly uses the verb 'delete', indicating irreversible removal of data.

Questions about linear_delete_milestone

What does the linear_delete_milestone tool do? +

linear_delete_milestone is a destructive tool on the All MCP server. It is categorised as a Destructive tool in the Allmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on linear_delete_milestone? +

Register the All MCP server in PolicyLayer and add a rule for linear_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 Allmcp. Nothing to install.

What risk level is linear_delete_milestone? +

linear_delete_milestone is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit linear_delete_milestone? +

Yes. Add a rate_limit block to the linear_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.

How do I block linear_delete_milestone completely? +

Set action: deny in the PolicyLayer policy for linear_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.

What MCP server provides linear_delete_milestone? +

linear_delete_milestone is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on All, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of All's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.