get_detailed_time_report
Get detailed time breakdown for a project. Shows total time grouped by issue and by employee. Supports date range filtering.
This record as markdown: /tools/dugynoo-huly-mcp/get-detailed-time-report.md
What get_detailed_time_report does on Huly
AI agents call get_detailed_time_report to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_detailed_time_report is rated Low
This tool retrieves and displays aggregated time tracking data filtered by date range. It performs queries and reporting only—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; worst case is unauthorized access to time tracking visibility, which is a confidentiality concern rather than operational risk.
From the tool's definition Tool name is 'get_detailed_time_report' and description states it 'Get detailed time breakdown for a project' and 'Shows total time grouped by issue and by employee' with 'date range filtering.' These are all read-only query operations with no modifications…
Attacks that exploit this kind of access
The rule that runs get_detailed_time_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_detailed_time_report, this is the rule to start with:
get_detailed_time_report is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every get_detailed_time_report call is checked against it from then on.
Questions about get_detailed_time_report
Get detailed time breakdown for a project. Shows total time grouped by issue and by employee. Supports date range filtering. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for get_detailed_time_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 Huly. Nothing to install.
get_detailed_time_report 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_detailed_time_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.
Set action: deny in the PolicyLayer policy for get_detailed_time_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.
get_detailed_time_report is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue