Get all budget months. Returns month summaries with income, budgeted, and activity totals.
AI agents call list_months 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 queries and returns budget month data without creating, modifying, or deleting any information. It is a straightforward read operation that retrieves summarized financial data for display purposes. While the data concerns finances, the tool itself performs no financial transactions, movements of money, or commitments—it only fetches existing budget summaries.
From the tool's definition Tool name is 'list_months' and description states it 'Get all budget months' and 'Returns month summaries' — purely a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Get all budget months. Returns month summaries with income, budgeted, and activity totals. 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_months: 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_months 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_months 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_months. 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_months 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 →