get_invoice_details
Full detail for one invoice — status, amounts, line items, payments, and balance due — found by invoice number or client name. Answers "what is on invoice 1042?" or "what does the Acme invoice still owe?"
This record as markdown: /tools/com-getsavitools-savi-tools/get-invoice-details.md
What get_invoice_details does on Savi Tools
AI agents call get_invoice_details 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 |
|---|---|---|---|
number_or_client | string | Yes | Invoice number or client name to look up. |
Parameters from the server's own tool schema.
Why get_invoice_details is rated Low
This tool exclusively retrieves financial records without modifying, deleting, or executing operations. It queries existing invoice data by invoice number or client name and returns read-only information. While it accesses financial data, it does not move money, create obligations, or change state—classification is Read, not Financial.
From the tool's definition Tool retrieves and queries invoice data: 'Full detail for one invoice — status, amounts, line items, payments, and balance due — found by invoice number or client name.' Verbs indicate data retrieval only: 'Answers "what is on invoice 1042?" or "what does the…
Attacks that exploit this kind of access
The rule that runs get_invoice_details 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_invoice_details, this is the rule to start with:
get_invoice_details 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_invoice_details call is checked against it from then on.
Questions about get_invoice_details
Full detail for one invoice — status, amounts, line items, payments, and balance due — found by invoice number or client name. Answers "what is on invoice 1042?" or "what does the Acme invoice still owe?". It is categorised as a Read tool in the Savi Tools MCP Server, which means it retrieves data without modifying state.
get_invoice_details accepts 1 parameter: number_or_client. Required: number_or_client. 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_invoice_details: 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_invoice_details 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_invoice_details 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_invoice_details. 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_invoice_details 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