High Risk →

start_time_tracking

Start time tracking on a task. Use taskId (preferred) or taskName + listName. Only one timer can run at a time.

Part of the ClickUp MCP - Premium MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke start_time_tracking to trigger processes or run actions in ClickUp MCP - Premium. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

start_time_tracking can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

taazkareem-clickup-mcp-premium.yaml
tools:
  start_time_tracking:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full ClickUp MCP - Premium policy for all 54 tools.

Tool Name start_time_tracking
Category Execute
Risk Level High

View all 54 tools →

Agents calling execute-class tools like start_time_tracking have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

start_time_tracking is one of the high-risk operations in ClickUp MCP - Premium. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the start_time_tracking tool do? +

Start time tracking on a task. Use taskId (preferred) or taskName + listName. Only one timer can run at a time.. It is categorised as a Execute tool in the ClickUp MCP - Premium MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_time_tracking? +

Add a rule in your Intercept YAML policy under the tools section for start_time_tracking. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the ClickUp MCP - Premium MCP server.

What risk level is start_time_tracking? +

start_time_tracking is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_time_tracking? +

Yes. Add a rate_limit block to the start_time_tracking rule in your Intercept 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 start_time_tracking completely? +

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

What MCP server provides start_time_tracking? +

start_time_tracking is provided by the ClickUp MCP - Premium MCP server (taazkareem/clickup-mcp-premium). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on ClickUp MCP - Premium

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.