Get all scheduled/recurring transactions for a budget.
AI agents call list_scheduled_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 queries and retrieves existing scheduled transaction data from YNAB without modifying, deleting, or executing any financial operations. It is a read-only operation that returns information about scheduled transactions for informational purposes only.
From the tool's definition Tool name 'list_scheduled_transactions' and description 'Get all scheduled/recurring transactions for a budget' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all scheduled/recurring transactions for a budget. 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_scheduled_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_scheduled_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_scheduled_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_scheduled_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_scheduled_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 →