Permanently delete a time entry, identified by its id.
AI agents call delete_time_entry to permanently remove resources in Clockify Time Tracking — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool falls into the Destructive category because it permanently removes data (a time entry record) in a way that cannot be reversed or recovered. Even though the data itself is not financial in nature, the irreversible deletion warrants the Destructive classification.
From the tool's definition Tool performs 'Permanently delete a time entry' — the word 'Permanently' and 'delete' clearly indicate an irreversible destruction action that cannot be undone.
Attacks that exploit this kind of access
Permanently delete a time entry, identified by its id. It is categorised as a Destructive tool in the Clockify Time Tracking MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Clockify Time Tracking MCP server in PolicyLayer and add a rule for delete_time_entry: 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 Clockify Time Tracking. Nothing to install.
delete_time_entry 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_time_entry 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_time_entry. 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_time_entry is provided by the Clockify Time Tracking MCP server (pypi:clockify-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 →