Low Risk

get_detailed_report

Generate a detailed time tracking report

How to control get_detailed_report ↓

What get_detailed_report does on Clockify MCP Server

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

Low Risk

Why get_detailed_report needs a policy

This tool retrieves and presents time tracking data without creating, modifying, or deleting any records. The use of 'get' and 'report' indicates a read-only operation. Even in the context of a time tracking system where financial implications exist downstream, this tool itself only queries and presents data.

From the tool's definition Tool name 'get_detailed_report' and description 'Generate a detailed time tracking report' indicate data retrieval and reporting functionality with no modification or deletion of records.

Documented attack patterns abuse exactly the kind of access get_detailed_report gives an agent:

How to control get_detailed_report

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_detailed_report:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_detailed_report": {}
  }
}

get_detailed_report is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Clockify MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_detailed_report

What does the get_detailed_report tool do? +

Generate a detailed time tracking report. 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_detailed_report? +

Register the Clockify MCP Server MCP server in PolicyLayer and add a rule for get_detailed_report: 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_detailed_report? +

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

Can I rate-limit get_detailed_report? +

Yes. Add a rate_limit block to the get_detailed_report 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_detailed_report completely? +

Set action: deny in the PolicyLayer policy for get_detailed_report. 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_detailed_report? +

get_detailed_report 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.

Enforce policy on every Clockify MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.