Get all accounts for a budget. Returns account names, types, balances, and status.
AI agents call list_accounts to retrieve information from YNAB 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 account information without creating, modifying, or deleting data. While it accesses sensitive financial data (account balances), it is read-only and has minimal blast radius if misused by an AI agent. The low severity reflects that exposure of account information is less critical than tools that can transfer money or delete transactions.
From the tool's definition Tool description states 'Get all accounts' and 'Returns account names, types, balances, and status' — purely retrieval operations with no modification or deletion.
Attacks that exploit this kind of access
Get all accounts for a budget. Returns account names, types, balances, and status. It is categorised as a Read tool in the YNAB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YNAB MCP Server MCP server in PolicyLayer and add a rule for list_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 YNAB MCP Server. Nothing to install.
list_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 list_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 list_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.
list_accounts is provided by the YNAB MCP Server MCP server (jeangnc/ynab-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 →