list_workspaces
AI agents call list_workspaces 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' verb is a standard indicator of read-only retrieval with no side effects. Listing workspaces retrieves metadata only without modifying, deleting, or executing operations. Low severity because workspace enumeration presents minimal risk even if misused by an AI agent. Confidence reduced slightly (0.85 vs. 1.0) due to empty description, but naming convention is unambiguous.
From the tool's definition Tool name 'list_workspaces' indicates retrieval/enumeration of workspace data. The description is empty, but the naming convention and position among sibling tools (which include write, execute, and financial operations) suggests this is a read-only query…
Attacks that exploit this kind of access
list_workspaces. 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_workspaces: 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_workspaces 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_workspaces 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_workspaces. 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_workspaces 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 →