get_user_weekly_summary

Get a summary of hours logged by a user for each week in the past month.

Server Clockify MCP Server keithhanson/clockify-mcp
Category Read
Risk class Low
Parameters 00 required

What get_user_weekly_summary does on Clockify MCP Server

AI agents call get_user_weekly_summary 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.

Why get_user_weekly_summary needs a policy

This tool retrieves and aggregates historical time tracking data for analysis purposes. It queries existing records without side effects, making it a Read operation. The severity is low because misuse would only expose time tracking information without enabling data modification or financial transactions. Confidence is high due to explicit language indicating data retrieval with no mutative operations.

From the tool's definition Tool description states 'Get a summary of hours logged by a user for each week in the past month' — a retrieval operation with no modification, creation, or deletion of data.

Questions about get_user_weekly_summary

What does the get_user_weekly_summary tool do? +

Get a summary of hours logged by a user for each week in the past month. It is categorised as a Read tool in the Clockify MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_user_weekly_summary? +

Register the Clockify MCP Server MCP server in PolicyLayer and add a rule for get_user_weekly_summary: 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.

What risk level is get_user_weekly_summary? +

get_user_weekly_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_user_weekly_summary? +

Yes. Add a rate_limit block to the get_user_weekly_summary 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.

How do I block get_user_weekly_summary completely? +

Set action: deny in the PolicyLayer policy for get_user_weekly_summary. 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.

What MCP server provides get_user_weekly_summary? +

get_user_weekly_summary is provided by the Clockify MCP Server MCP server (keithhanson/clockify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.