AI agents call delete-habit-logs-range 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 irreversibly deletes data (habit logs) across a date range with no undo capability. Destructive is the appropriate category as it is more severe than Write. Severity is high because bulk deletion of user data by date range could result in significant loss of personal tracking records if misused by an AI agent (e.g., deleting the wrong date range).
From the tool's definition Tool name 'delete-habit-logs-range' explicitly performs deletion; description states 'Delete habit logs in date range'. The server description confirms this tool is for 'deleting...habit logs'.
Documented attack patterns abuse exactly the kind of access delete-habit-logs-range 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-logs-range:
{
"version": "1",
"default": "deny",
"hide": [
"delete-habit-logs-range"
]
}delete-habit-logs-range 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 habit logs in date range. 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-logs-range: 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-logs-range 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-logs-range 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-logs-range. 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-logs-range 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.