list_recent_expenses
List the most recent expenses, newest first, optionally filtered by category. Answers "what are my latest expenses?"
This record as markdown: /tools/com-getsavitools-savi-tools/list-recent-expenses.md
What list_recent_expenses does on Savi Tools
AI agents call list_recent_expenses 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 |
|---|---|---|---|
limit | integer | — | How many to return (default 10, max 50). |
category | string | — | Optional category name to filter to. |
Parameters from the server's own tool schema.
Why list_recent_expenses is rated Low
This tool retrieves and displays expense records without any capability to create, modify, delete, or execute operations. It is a straightforward read-only query that answers a passive information request. The context (business expense tracking via Savi Tools) and sibling tools (all get_* functions) reinforce that this is a data retrieval operation. No side effects or irreversible actions are possible.
From the tool's definition Tool description states 'List the most recent expenses' and 'optionally filtered by category' — pure query/retrieval with no modification capability. Name contains 'list' indicating enumeration of existing data.
Attacks that exploit this kind of access
The rule that runs list_recent_expenses 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 list_recent_expenses, this is the rule to start with:
list_recent_expenses 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 list_recent_expenses call is checked against it from then on.
Questions about list_recent_expenses
List the most recent expenses, newest first, optionally filtered by category. Answers "what are my latest expenses?". It is categorised as a Read tool in the Savi Tools MCP Server, which means it retrieves data without modifying state.
list_recent_expenses accepts 2 parameters: limit, category. 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 list_recent_expenses: 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.
list_recent_expenses 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 list_recent_expenses 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 list_recent_expenses. 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.
list_recent_expenses 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