Delete a time registration by its GUID.
AI agents call delete_time_registration to permanently remove resources in Timelog — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call delete_time_registration doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Timelog is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Delete a time registration by its GUID. It is categorised as a Destructive tool in the Timelog MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Timelog MCP server in PolicyLayer and add a rule for delete_time_registration: 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 Timelog. Nothing to install.
delete_time_registration 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_registration 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_registration. 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_registration is provided by the Timelog MCP server (timelog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.