get_user_scheduling_totals
AI agents call get_user_scheduling_totals 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 fetches or calculates user scheduling totals, which is a read operation with no side effects. No data modification, deletion, or external execution occurs. The low blast radius of misuse—returning potentially unwanted scheduling data—makes it a low-severity read risk.
From the tool's definition Tool name 'get_user_scheduling_totals' indicates a retrieval operation ('get') that queries aggregated scheduling data. Empty description limits confidence, but the 'get_' prefix and 'totals' suffix are characteristic of read-only data retrieval patterns.
Attacks that exploit this kind of access
get_user_scheduling_totals. 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 get_user_scheduling_totals: 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.
get_user_scheduling_totals 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_user_scheduling_totals 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_user_scheduling_totals. 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_user_scheduling_totals 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 →