list_holidays_in_period
AI agents call list_holidays_in_period to retrieve information from Clockify Time Tracking without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries holiday information for a specified period with no indicated side effects, reversible actions, code execution, destructive operations, or financial implications. The absence of description reduces confidence slightly, but the naming pattern is consistent with read-only operations on a time-tracking platform.
From the tool's definition Tool name 'list_holidays_in_period' indicates retrieval/query of holiday data without modification. The empty description prevents confirmation of side effects, but naming convention strongly suggests a simple list/read operation.
Attacks that exploit this kind of access
list_holidays_in_period. It is categorised as a Read tool in the Clockify Time Tracking MCP Server, which means it retrieves data without modifying state.
Register the Clockify Time Tracking MCP server in PolicyLayer and add a rule for list_holidays_in_period: 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.
list_holidays_in_period is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_holidays_in_period 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 list_holidays_in_period. 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.
list_holidays_in_period 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 →