get_task_time_entries

Gets all time entries for a task with filtering options. Use taskId (preferred) or taskName + optional listName. Returns all tracked time with user info, descriptions, tags, start/end times, and durations.

Server ClickUp MCP twofeetup/clickup-mcp
Category Read
Risk class Low
Parameters 00 required

What get_task_time_entries does on ClickUp MCP

AI agents call get_task_time_entries to retrieve information from ClickUp MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_task_time_entries needs a policy

This tool retrieves and queries time entry data associated with a task. It performs a read-only operation that returns information (user info, descriptions, tags, start/end times, durations) without creating, modifying, deleting, or executing any actions. The 'filtering options' mentioned are query parameters, not side-effecting operations. This clearly fits the Read category.

From the tool's definition Tool name 'get_task_time_entries' and description 'Gets all time entries for a task' with 'Returns all tracked time' indicate retrieval of existing data with no modification or side effects.

Questions about get_task_time_entries

What does the get_task_time_entries tool do? +

Gets all time entries for a task with filtering options. Use taskId (preferred) or taskName + optional listName. Returns all tracked time with user info, descriptions, tags, start/end times, and durations. It is categorised as a Read tool in the ClickUp MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_task_time_entries? +

Register the ClickUp MCP server in PolicyLayer and add a rule for get_task_time_entries: 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.

What risk level is get_task_time_entries? +

get_task_time_entries is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_task_time_entries? +

Yes. Add a rate_limit block to the get_task_time_entries 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.

How do I block get_task_time_entries completely? +

Set action: deny in the PolicyLayer policy for get_task_time_entries. 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.

What MCP server provides get_task_time_entries? +

get_task_time_entries 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.