Permanently delete an expense from a workspace.
AI agents call delete_expense 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 irreversibly removes data (an expense record) that cannot be recovered. It matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the blast radius is limited to expense records rather than the entire system, permanent deletion of financial records in a time-tracking/invoicing context presents a high severity risk if misused by an AI…
From the tool's definition Tool name is 'delete_expense' and description states 'Permanently delete an expense from a workspace.' The word 'Permanently' and 'delete' indicate irreversible data loss.
Attacks that exploit this kind of access
Permanently delete an expense from a workspace. 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_expense: 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_expense 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_expense 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_expense. 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_expense 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 →