stop_timer · ClickUp MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_timer does on ClickUp MCP Server

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

WHY IT NEEDS A POLICY

Why stop_timer needs a policy

Stopping a timer modifies the state of an active time tracking session. This is a reversible write operation (you can start a new timer), not destructive. Misuse could result in incorrect time records but no irreversible data loss.

From the tool's definition Stop tracking time

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_timer Rate-limited

stop_timer 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_timer": {
      "limits": [
        {
          "counter": "stop_timer_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 Server, so you can run agents against it safely.

FAQ

Questions about stop_timer

What does the stop_timer tool do? +

Stop tracking time. It is categorised as a Write tool in the ClickUp MCP Server 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_timer? +

Register the ClickUp MCP Server MCP server in PolicyLayer and add a rule for stop_timer: 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 Server. Nothing to install.

What risk level is stop_timer? +

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

Can I rate-limit stop_timer? +

Yes. Add a rate_limit block to the stop_timer 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_timer completely? +

Set action: deny in the PolicyLayer policy for stop_timer. 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_timer? +

stop_timer is provided by the ClickUp MCP Server MCP server (smeric28/clickup-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.