AI agents call delete-habit-log to permanently remove resources in Habitify — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes habit log entries, which cannot be undone. Deletion of user data is irreversible and represents a destructive action. While not critical (no financial or system-level impact), the high severity reflects that an agent misusing this tool could erase user's habit tracking history. Confidence is high because the intent is unambiguous from both name and description.
From the tool's definition Tool name is 'delete-habit-log' and description states 'Delete a specific habit log'. The verb 'delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete-habit-log gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Habitify, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-habit-log:
{
"version": "1",
"default": "deny",
"hide": [
"delete-habit-log"
]
}delete-habit-log disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a specific habit log. It is categorised as a Destructive tool in the Habitify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Habitify MCP server in PolicyLayer and add a rule for delete-habit-log: 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 Habitify. Nothing to install.
delete-habit-log 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-habit-log 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-habit-log. 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-habit-log is provided by the Habitify MCP server (sargonpiraev/habitify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Habitify, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Habitify tools catalogued and risk-classified — across an index of 43,000+ MCP servers.