delete_milestone
Permanently delete a Huly milestone. This action cannot be undone.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-milestone.md
What delete_milestone does on Huly
AI agents call delete_milestone to permanently remove resources in Huly, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_milestone is rated Critical
This tool irreversibly deletes data (a milestone in Huly). It matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' Severity is high because deleted milestones could impact project planning and tracking, though the blast radius is limited to a single milestone object rather than a complete database or financial system (which would be critical).
From the tool's definition Tool description explicitly states 'Permanently delete a Huly milestone. This action cannot be undone.' The words 'delete' and 'cannot be undone' clearly indicate irreversible data destruction.
Attacks that exploit this kind of access
The rule that runs delete_milestone safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_milestone, this is the rule to start with:
delete_milestone is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every delete_milestone call is checked against it from then on.
Questions about delete_milestone
Permanently delete a Huly milestone. This action cannot be undone. It is categorised as a Destructive tool in the Huly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Huly 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 Huly. 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 Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
Across the catalogue