find_user_team_manager
AI agents call find_user_team_manager 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 tool appears to fetch or query manager information associated with a user, which is a non-destructive read operation. While the description is empty (lowering confidence slightly), the function name strongly suggests it retrieves existing data without modifying, deleting, or executing external operations. In a time-tracking context, finding a manager is a lookup/search operation typical of Read category tools.
From the tool's definition Tool name 'find_user_team_manager' indicates a query/lookup operation that retrieves manager information for a user. The empty description provides no conflicting evidence.
Attacks that exploit this kind of access
find_user_team_manager. 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 find_user_team_manager: 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.
find_user_team_manager 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_user_team_manager 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_user_team_manager. 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_user_team_manager 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 →