Get Lunch Money transactions with optional filters.
AI agents call get_transactions to retrieve information from Lunch Money MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves financial transaction data without creating, modifying, deleting, or executing any operations. While the data itself may be sensitive (personal finance records), the tool's function is purely informational Read access. Misuse would expose data but not cause financial harm, data loss, or unintended operations.
From the tool's definition Tool name 'get_transactions' and description 'Get Lunch Money transactions with optional filters' indicate a retrieval operation with no modification or destructive capability.
Attacks that exploit this kind of access
Get Lunch Money transactions with optional filters. It is categorised as a Read tool in the Lunch Money MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lunch Money MCP Server MCP server in PolicyLayer and add a rule for get_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 Lunch Money MCP Server. Nothing to install.
get_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_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_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_transactions is provided by the Lunch Money MCP Server MCP server (robshox/lunchmoney-mcp). 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 →