AI agents call get_workspace_users 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 user information from a workspace without creating, modifying, or deleting any data. It is a straightforward read operation that queries existing data and returns it to the caller. The absence of mutation verbs (create, update, delete) and the presence of 'get' confirms this is a Read category tool with low severity, as workspace user lists are typically non-sensitive operational metadata.
From the tool's definition Tool name 'get_workspace_users' and description 'Get all users in a workspace' indicate a query/retrieval operation with no data modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access get_workspace_users gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Clockify MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_workspace_users:
{
"version": "1",
"default": "deny",
"tools": {
"get_workspace_users": {}
}
}get_workspace_users is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all users in a workspace. 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 get_workspace_users: 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.
get_workspace_users 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 get_workspace_users 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 get_workspace_users. 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.
get_workspace_users is provided by the Clockify MCP Server MCP server (ratheesh-aot/clockify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Clockify MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Clockify MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.