Get budget summary for a specific time period
AI agents call get-budget-summary to retrieve information from Lunchmoney without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries financial summary data from the Lunchmoney service. It performs a read-only operation to fetch budget information for analysis purposes. No data is created, modified, deleted, or financial transactions are executed. While it involves financial data, the tool itself does not move money or commit financial obligations—it only queries existing budget information.
From the tool's definition Tool name 'get-budget-summary' and description 'Get budget summary for a specific time period' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get budget summary for a specific time period. It is categorised as a Read tool in the Lunchmoney MCP Server, which means it retrieves data without modifying state.
Register the Lunchmoney MCP server in PolicyLayer and add a rule for get-budget-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 Lunchmoney. Nothing to install.
get-budget-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-budget-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-budget-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-budget-summary is provided by the Lunchmoney MCP server (lunchmoney-mcp-server). 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 →