Find all time entries for a specific project.
AI agents call find_project_time_entries to retrieve information from Clockify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical time entry data for reporting or analysis purposes. It has no side effects, does not modify data, and does not trigger external operations. The blast radius of misuse is limited to potential information disclosure (viewing time records), which is a low-severity Read operation.
From the tool's definition Tool description states 'Find all time entries for a specific project' — a retrieval operation with no modification or deletion. The verb 'find' and the lack of any write/delete/execute language confirm this is a query operation.
Attacks that exploit this kind of access
Find all time entries for a specific project. It is categorised as a Read tool in the Clockify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Clockify MCP Server MCP server in PolicyLayer and add a rule for find_project_time_entries: 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 MCP Server. Nothing to install.
find_project_time_entries 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 find_project_time_entries 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 find_project_time_entries. 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.
find_project_time_entries is provided by the Clockify MCP Server MCP server (keithhanson/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 →