Get transactions for a budget. Supports filtering by date, type, category, payee, and account.
AI agents call list_transactions 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 and queries transaction data from a YNAB budget with optional filters. It performs no creation, modification, deletion, or execution of external operations. The only potential concern is that transaction data may contain sensitive financial information, but the severity remains low as the tool itself is read-only with no irreversible impact.
From the tool's definition Tool name 'list_transactions' and description 'Get transactions' indicates data retrieval. The phrase 'Supports filtering by date, type, category, payee, and account' confirms query functionality with no side effects.
Attacks that exploit this kind of access
Get transactions for a budget. Supports filtering by date, type, category, payee, and account. 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_transactions: 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_transactions 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_transactions 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_transactions. 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_transactions 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 →