Delete a time entry
AI agents call delete_time_entry to permanently remove resources in Tonle OpenProject MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes time entry records, which cannot be undone. Time entries are critical audit records for billing, payroll, and project tracking. Deletion is irreversible and could cause financial reconciliation issues, loss of accountability, and data integrity problems. While not directly financial, the impact on time-tracking systems that feed into billing makes this a high-severity destructive action.
From the tool's definition Tool name 'delete_time_entry' and description 'Delete a time entry' explicitly perform irreversible deletion of time tracking data.
Attacks that exploit this kind of access
Delete a time entry. It is categorised as a Destructive tool in the Tonle OpenProject MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tonle OpenProject MCP Server 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 Tonle OpenProject MCP Server. 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 Tonle OpenProject MCP Server MCP server (liratanak/openproject-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 →