Delete time from a specific task using the /tasks/{id}/time endpoint.
AI agents call everhour_delete_task_time to permanently remove resources in Everhour — 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 everhour_delete_task_time doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Everhour is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Delete time from a specific task using the /tasks/{id}/time endpoint. It is categorised as a Destructive tool in the Everhour MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Everhour MCP server in PolicyLayer and add a rule for everhour_delete_task_time: 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 Everhour. Nothing to install.
everhour_delete_task_time 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 everhour_delete_task_time 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 everhour_delete_task_time. 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.
everhour_delete_task_time is provided by the Everhour MCP server (stefanskiasan/everhour-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.