get_mileage_summary
Total business miles and IRS mileage deduction for a calendar year, with a per-type breakdown. Answers "what is my mileage deduction so far this year?"
This record as markdown: /tools/com-getsavitools-savi-tools/get-mileage-summary.md
What get_mileage_summary does on Savi Tools
AI agents call get_mileage_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 |
|---|---|---|---|
year | integer | — | Calendar year, e.g. 2026. Defaults to the current year. |
Parameters from the server's own tool schema.
Why get_mileage_summary is rated Low
This tool only retrieves and summarizes existing mileage and deduction data for informational purposes. It answers a query ('what is my mileage deduction so far this year?') without creating, modifying, deleting, or executing external operations. No financial transactions are triggered—it simply returns calculated summaries. This is a straightforward read/query operation with minimal risk.
From the tool's definition Tool provides retrieval of 'Total business miles and IRS mileage deduction' data with no ability to modify or delete; verb 'get_' confirms read-only intent; query pattern typical of dashboard/summary retrieval.
Attacks that exploit this kind of access
The rule that runs get_mileage_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_mileage_summary, this is the rule to start with:
get_mileage_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_mileage_summary call is checked against it from then on.
Questions about get_mileage_summary
Total business miles and IRS mileage deduction for a calendar year, with a per-type breakdown. Answers "what is my mileage deduction so far this year?". It is categorised as a Read tool in the Savi Tools MCP Server, which means it retrieves data without modifying state.
get_mileage_summary accepts 1 parameter: year. 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_mileage_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_mileage_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_mileage_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_mileage_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_mileage_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