clockify_action
Perform a Clockify action: get_clockify_workspaces, get_time_entries, create_time_entry, get_clockify_projects, get_clockify_summary.
This record as markdown: /tools/creativelead-unclick/clockify-action.md
What clockify_action does on UnClick
AI agents use clockify_action to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | string | — | |
start | string | — | |
action | string | — | |
api_key | string | — | |
project_id | string | — | |
description | string | — | |
workspace_id | string | — |
Parameters from the server's own tool schema.
Why clockify_action is rated Medium
The tool spans Read and Write operations. The most severe applicable category is Write due to 'create_time_entry', which creates new data in Clockify. The read operations (get_*) are lower severity but do not override the Write classification. Misuse could result in fabricated time entries in accounting/billing systems, hence medium severity.
From the tool's definition create_time_entry listed as one of the actions; also includes get_clockify_workspaces, get_time_entries, get_clockify_projects, get_clockify_summary
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs clockify_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clockify_action, this is the rule to start with:
clockify_action 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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every clockify_action call is checked against it from then on.
Questions about clockify_action
Perform a Clockify action: get_clockify_workspaces, get_time_entries, create_time_entry, get_clockify_projects, get_clockify_summary. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
clockify_action accepts 7 parameters: end, start, action, api_key, project_id, description, workspace_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for clockify_action: 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 UnClick. Nothing to install.
clockify_action is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the clockify_action 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.
Set action: deny in the PolicyLayer policy for clockify_action. 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.
clockify_action is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue