Get aggregated time tracking summary for a date range.
AI agents call time_summary to retrieve information from Rhizm MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves aggregated time tracking data within a specified date range. It performs no modifications, deletions, or external operations. The operation is purely informational, making it a straightforward Read category tool with low severity since it only accesses existing data without any ability to alter system state or cause harm.
From the tool's definition Tool name 'time_summary' and description 'Get aggregated time tracking summary for a date range' indicate a retrieval operation with no modification or side effects. The verb 'Get' and 'summary' clearly denote a read-only query operation.
Attacks that exploit this kind of access
Get aggregated time tracking summary for a date range. It is categorised as a Read tool in the Rhizm MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rhizm MCP Server MCP server in PolicyLayer and add a rule for time_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 Rhizm MCP Server. Nothing to install.
time_summary 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 time_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.
Set action: deny in the PolicyLayer policy for time_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.
time_summary is provided by the Rhizm MCP Server MCP server (rhizmapp/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 →