List Lunch Money Plaid-connected accounts.
AI agents call get_plaid_accounts 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 and lists existing Plaid-connected accounts without creating, modifying, deleting, or executing any operations. It is a straightforward read operation. Severity is low because the data exposed (connected account information) is financial metadata that the authenticated user already controls, and unauthorized exposure would be limited to the user's own account linkages.
From the tool's definition Tool name is 'get_plaid_accounts' and description states 'List Lunch Money Plaid-connected accounts' — a pure retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List Lunch Money Plaid-connected accounts. 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_plaid_accounts: 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_plaid_accounts 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_plaid_accounts 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_plaid_accounts. 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_plaid_accounts 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 →