List recent transactions, optionally filtered by date, account, or category.
AI agents call ynab_get_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 with optional filtering parameters. It performs no writes, deletions, or financial operations—only reads from the user's YNAB budget data. The blast radius of misuse is minimal since it only exposes existing data visibility; an AI agent cannot modify finances or cause financial harm through this tool alone.
From the tool's definition Tool name includes 'get_transactions' and description states 'List recent transactions, optionally filtered by date, account, or category' — a pure retrieval operation with no modification capability.
Attacks that exploit this kind of access
List recent transactions, optionally filtered by date, account, or category. 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_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.
ynab_get_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 ynab_get_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 ynab_get_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.
ynab_get_transactions 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.
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 →