Track time on tasks. Actions: get_entries (retrieve), start (begin timer), stop (end timer), add_entry (manual entry), delete_entry (remove entry), get_current (running timer). Flexible task identification: taskId, taskName, or customTaskId. Supports duration in multiple formats and billable/tags...
AI agents call task_time_tracking to permanently remove resources in ClickUp MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool consolidates multiple actions under one interface. While most actions (get_entries, start, stop, add_entry, get_current) are Read or Write, the presence of 'delete_entry (remove entry)' makes this Destructive per the rules requiring the most severe category.
From the tool's definition delete_entry (remove entry) — the tool explicitly supports deleting time entries, which is an irreversible action. Also includes write-level actions: start, stop, add_entry. Most severe applicable category is Destructive due to delete_entry.
Attacks that exploit this kind of access
Track time on tasks. Actions: get_entries (retrieve), start (begin timer), stop (end timer), add_entry (manual entry), delete_entry (remove entry), get_current (running timer). Flexible task identification: taskId, taskName, or customTaskId. Supports duration in multiple formats and billable/tags metadata. It is categorised as a Destructive tool in the ClickUp MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ClickUp MCP server in PolicyLayer and add a rule for task_time_tracking: 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 ClickUp MCP. Nothing to install.
task_time_tracking 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 task_time_tracking 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 task_time_tracking. 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.
task_time_tracking is provided by the ClickUp MCP server (twofeetup/clickup-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 →