stop_time_tracking · ClickUp MCP: Risk & Policy

WHAT IT DOES

What stop_time_tracking does on ClickUp MCP

AI agents use stop_time_tracking to create or update resources in ClickUp MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClickUp MCP environment.

WHY IT NEEDS A POLICY

Why stop_time_tracking needs a policy

This tool modifies the state of an active time entry by stopping it, which is a reversible write operation (time entries can be restarted or adjusted). It does not delete data, execute code, or involve financial transactions. Misuse could disrupt time tracking records but the blast radius is limited.

From the tool's definition Stops the currently running time tracker... Returns the completed time entry details.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_time_tracking Rate-limited

stop_time_tracking stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_time_tracking": {
      "limits": [
        {
          "counter": "stop_time_tracking_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ClickUp MCP, so you can run agents against it safely.

FAQ

Questions about stop_time_tracking

What does the stop_time_tracking tool do? +

Stops the currently running time tracker. Optional fields: description and tags. Returns the completed time entry details. It is categorised as a Write tool in the ClickUp MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on stop_time_tracking? +

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

What risk level is stop_time_tracking? +

stop_time_tracking is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit stop_time_tracking? +

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

How do I block stop_time_tracking completely? +

Set action: deny in the PolicyLayer policy for stop_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 stop_time_tracking? +

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