duplicate_time_entry · Clockify Time Tracking MCP

WHAT IT DOES

What duplicate_time_entry does on Clockify Time Tracking

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

WHY IT NEEDS A POLICY

Why duplicate_time_entry needs a policy

Duplicating a time entry creates a new, reversible data record. While it modifies the system state by adding data, it is not destructive (no deletion/overwriting), not financial (no money movement), and not execute (no arbitrary code/command execution). This is a write operation that can be undone by deleting the duplicated entry.

From the tool's definition Tool description states 'Duplicate one of a user's time entries, creating a copy' - this creates new data (a duplicate time entry) in the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

duplicate_time_entry Rate-limited

duplicate_time_entry 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": {
    "duplicate_time_entry": {
      "limits": [
        {
          "counter": "duplicate_time_entry_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 Time Tracking, so you can run agents against it safely.

FAQ

Questions about duplicate_time_entry

What does the duplicate_time_entry tool do? +

Duplicate one of a user's time entries, creating a copy. It is categorised as a Write tool in the Clockify Time Tracking MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on duplicate_time_entry? +

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

What risk level is duplicate_time_entry? +

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

Can I rate-limit duplicate_time_entry? +

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

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

duplicate_time_entry is provided by the Clockify Time Tracking MCP server (pypi:clockify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.