update_holiday
AI agents use update_holiday 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.
The tool modifies holiday records, which is reversible (can be updated again) but impacts payroll, time-off calculations, and organizational policies. This fits Write rather than Read (retrieves data) or Destructive (irreversible deletion). Severity is medium because holiday changes affect multiple users' time-off entitlements and pay calculations, but the impact is typically remediable.
From the tool's definition Tool name 'update_holiday' indicates modification of holiday data. The empty description prevents direct confirmation of scope, but within a time-tracking system, updating holidays affects time-off policies and accruals that other users depend on.
Attacks that exploit this kind of access
update_holiday. 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.
Register the Clockify Time Tracking MCP server in PolicyLayer and add a rule for update_holiday: 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.
update_holiday 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 update_holiday 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 update_holiday. 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.
update_holiday 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →