Get recent transactions
AI agents call get-recent-transactions 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 transaction history from Lunchmoney without making any changes to the data. It is a straightforward query operation that has no side effects. The Lunchmoney server context (personal finance management) and sibling tools (get-budget-summary, get-category-spending, search-transactions) further confirm this is a read-only data access pattern.
From the tool's definition Tool name 'get-recent-transactions' and description 'Get recent transactions' indicate data retrieval with no modification. The verb 'Get' and lack of any action verbs (create, update, delete, modify) confirm read-only operation.
Attacks that exploit this kind of access
Get recent transactions. 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-recent-transactions: 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-recent-transactions 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-recent-transactions 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-recent-transactions. 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-recent-transactions 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 →