Get details of a specific transaction
AI agents call get_single_transaction 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 transaction details without creating, modifying, deleting, or executing side effects. Although it operates on financial data within a financial management system, the tool itself performs only read-only access. The severity is low because retrieval of existing transaction data has minimal risk if misused by an AI agent—it cannot alter financial state or commit obligations.
From the tool's definition Tool name 'get_single_transaction' and description 'Get details of a specific transaction' indicate data retrieval without modification. The action is a query/fetch operation.
Attacks that exploit this kind of access
Get details of a specific transaction. 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_single_transaction: 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_single_transaction 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_single_transaction 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_single_transaction. 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_single_transaction is provided by the Lunch Money MCP Server MCP server (matiasl13/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 →