list_time_off_policies
AI agents call list_time_off_policies 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.
The 'list' prefix is characteristically associated with Read operations that retrieve data. No side effects, modifications, or irreversible actions are implied by the name. Despite the empty description lowering confidence slightly, the naming convention and server context (time-tracking management) indicate this is a non-destructive data retrieval tool.
From the tool's definition Tool name 'list_time_off_policies' indicates a retrieval operation with the 'list' verb. The description is empty, but the naming pattern and context of a time-tracking server strongly suggest this queries or retrieves existing policies without modification.
Attacks that exploit this kind of access
list_time_off_policies. 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_time_off_policies: 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_time_off_policies 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_time_off_policies 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_time_off_policies. 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_time_off_policies 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 →