list_clients
AI agents call list_clients 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_clients' tool retrieves or queries client data with no side effects. This is a Read operation. Severity is low because listing clients has minimal blast radius—it exposes metadata but cannot modify, delete, or financially impact data. Confidence is 0.85 rather than higher only because the description is empty, requiring inference from the tool name and server context.
From the tool's definition Tool name 'list_clients' indicates a query/retrieval operation. The description is empty, but the name and context (Clockify time-tracking server with sibling tools like create_client, create_expense) strongly suggest this lists existing client records…
Attacks that exploit this kind of access
list_clients. 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_clients: 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_clients 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_clients 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_clients. 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_clients 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 →