delete_todo
Delete a Planner ToDo. This is destructive; deleting the last open issue ToDo can cause Huly classic issue status automation.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-todo.md
What delete_todo does on Huly
AI agents call delete_todo 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_todo is rated Critical
This tool irreversibly deletes a ToDo item and can trigger unintended automation effects in the Huly system. Destructive operations that permanently remove data and cannot be undone represent the most severe category beyond Execute. The explicit warning about automation side effects elevates the risk from Write to Destructive.
From the tool's definition Tool name is 'delete_todo' and description explicitly states 'This is destructive; deleting the last open issue ToDo can cause Huly classic issue status automation.' The description uses the word 'destructive' and indicates irreversible deletion with…
Attacks that exploit this kind of access
The rule that runs delete_todo 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_todo, this is the rule to start with:
delete_todo 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_todo call is checked against it from then on.
Questions about delete_todo
Delete a Planner ToDo. This is destructive; deleting the last open issue ToDo can cause Huly classic issue status automation. 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_todo: 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_todo 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_todo 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_todo. 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_todo 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