start_timer · Clockify MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_timer does on Clockify MCP Server

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

WHY IT NEEDS A POLICY

Why start_timer needs a policy

Starting a timer creates a new active time entry in Clockify. This is a Write operation as it creates data that can be reversed (stopped or deleted). It does not execute code, delete data, or involve financial transactions. Severity is medium because misuse could create unwanted time entries affecting billing records and team reporting.

From the tool's definition 'Start a timer for the current user' — initiates a new timer/time entry, which is a reversible write operation (can be stopped or deleted)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_timer Rate-limited

start_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": {
    "start_timer": {
      "limits": [
        {
          "counter": "start_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 Clockify MCP Server, so you can run agents against it safely.

FAQ

Questions about start_timer

What does the start_timer tool do? +

Start a timer for the current user. It is categorised as a Write tool in the Clockify 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 start_timer? +

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

What risk level is start_timer? +

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

Can I rate-limit start_timer? +

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

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

start_timer is provided by the Clockify MCP Server MCP server (keithhanson/clockify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.