Delete a checklist item.
AI agents call delete_checklist_item to permanently remove resources in Habitca — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a checklist item from a task). Deletion is a destructive operation that cannot be reversed. Although the blast radius is limited to a single checklist item rather than entire tasks or accounts, it still qualifies as Destructive rather than Write because the action is permanent and cannot be easily recovered.
From the tool's definition delete_checklist_item - the word 'Delete' explicitly indicates irreversible removal of data. The tool name directly states it removes a checklist item, which cannot be undone.
Attacks that exploit this kind of access
Delete a checklist item. It is categorised as a Destructive tool in the Habitca MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Habitca MCP server in PolicyLayer and add a rule for delete_checklist_item: 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 Habitca. Nothing to install.
delete_checklist_item 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_checklist_item 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_checklist_item. 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_checklist_item is provided by the Habitca MCP server (leon-jarvis1/habitca_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 →