delete_todo
Hard-deletes a todo and any comments on it. Use sparingly: prefer drop_todo so history is preserved. agent_id required for the audit log.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/delete-todo.md
What delete_todo does on UnClick
AI agents call delete_todo to permanently remove resources in UnClick, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
todo_id | string | Yes | |
agent_id | string | Yes |
Parameters from the server's own tool schema.
Why delete_todo is rated Critical
This tool permanently removes data (todo records and associated comments) without the ability to undo the operation. Hard deletion is a destructive action that erases audit trails unless mitigated by the audit_log parameter.
From the tool's definition Tool description explicitly states 'Hard-deletes a todo and any comments on it' and warns to 'Use sparingly: prefer drop_todo so history is preserved.' The language 'hard-delete' and contrast with a softer alternative confirm irreversible data removal.
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 UnClick, 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 UnClick, apply this rule, and every delete_todo call is checked against it from then on.
Questions about delete_todo
Hard-deletes a todo and any comments on it. Use sparingly: prefer drop_todo so history is preserved. agent_id required for the audit log. It is categorised as a Destructive tool in the UnClick MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_todo accepts 2 parameters: todo_id, agent_id. Required: todo_id, agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick 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 UnClick. 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 UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue