get_time_summary
Hours logged over a period, split billable vs. non-billable and broken down by project. Answers "how many hours did I bill last month?"
This record as markdown: /tools/com-getsavitools-savi-tools/get-time-summary.md
What get_time_summary does on Savi Tools
AI agents call get_time_summary to retrieve information from Savi Tools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
period | string | — | A 4-digit year, or this_year / last_year / this_quarter / last_quarter. Omit for the current fiscal year. |
project | string | — | Optional project name to filter to. |
Parameters from the server's own tool schema.
Why get_time_summary is rated Low
This tool queries and summarizes historical time-tracking data. It performs a read-only operation with no side effects, no code execution, and no ability to modify or delete records. The blast radius of misuse is minimal—an AI could only retrieve business metrics the user has already recorded. This aligns with the Read category definition: 'retrieves or queries data; no side effects.'
From the tool's definition Tool description states it retrieves 'Hours logged over a period, split billable vs. non-billable and broken down by project' and answers 'how many hours did I bill last month?' — purely data retrieval with no modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs get_time_summary safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Savi Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_time_summary, this is the rule to start with:
get_time_summary 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 Savi Tools, apply this rule, and every get_time_summary call is checked against it from then on.
Questions about get_time_summary
Hours logged over a period, split billable vs. non-billable and broken down by project. Answers "how many hours did I bill last month?". It is categorised as a Read tool in the Savi Tools MCP Server, which means it retrieves data without modifying state.
get_time_summary accepts 2 parameters: period, project. The full parameter table on this page comes from the server's own tool schema.
Register the Savi Tools MCP server in PolicyLayer and add a rule for get_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 Savi Tools. Nothing to install.
get_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 get_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 get_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.
get_time_summary is provided by the Savi Tools MCP server (https://getsavitools.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Savi Tools, and thousands of servers like it.
This server
Across the catalogue