List all budgets available to the authenticated user.
AI agents call ynab_get_budgets 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 only queries and returns budget metadata available to the user. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an AI could learn which budgets exist, but cannot alter financial data or move money. Classified as Read with low severity.
From the tool's definition Tool name includes 'get' and description states 'List all budgets' — a read-only operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
List all budgets available to the authenticated user. 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 ynab_get_budgets: 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.
ynab_get_budgets 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 ynab_get_budgets 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 ynab_get_budgets. 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.
ynab_get_budgets is provided by the YNAB MCP Server MCP server (wgdevelopment/ynab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ynab_get_budgets is one line of YNAB MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →