// SCAN REPORT

YNAB MCP Server

25 tools. 10 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated: 4 Jul 2026

10 can modify or destroy data

15 read-only

25 tools total

Community server · catalogue entry verified 04/07/2026

How to control YNAB MCP Server ↓

TOOL MAP

What YNAB MCP Server exposes to your agents

Read (15) Write / Execute (7) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous YNAB MCP Server tools

Destructive · High delete_scheduled_transaction This tool permanently removes a scheduled transaction record from YNAB, which cannot be undone. Destructive · High delete_transaction This tool permanently removes transaction records from a financial management system. Destructive · High undo_operation Undoing a write operation irreversibly removes or negates previously committed changes. Write · Medium create_account This tool creates a new account, which is a write operation that modifies budget structure.

10 of YNAB MCP Server's 25 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control YNAB MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and YNAB MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_scheduled_transaction": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_account": {
    "limits": [
      {
        "counter": "create_account_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_account": {
    "limits": [
      {
        "counter": "get_account_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register YNAB MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON YNAB →

Instant setup, no code required.

FULL CATALOGUE

All 25 YNAB MCP Server tools

DESTRUCTIVE 3 tools

Destructive delete_scheduled_transaction Delete an existing scheduled transaction. Destructive delete_transaction Delete an existing transaction. Destructive undo_operation Revert a previous write operation by its history entry ID. Note: Account creation cannot be undone (YNAB API l

WRITE 7 tools

Write create_account Create a new account in the budget. Write create_scheduled_transaction Create a new scheduled/recurring transaction. Date must be in the future (max 5 years). Write create_transaction Create a new transaction. Amount should be negative for expenses and positive for income. Write update_category_budget Update the budgeted amount for a category in a specific month. Write update_payee Update a payee Write update_scheduled_transaction Update an existing scheduled transaction. Only provide fields you want to change. Write update_transaction Update an existing transaction. Only provide the fields you want to change.

READ 15 tools

Read get_account Get detailed information about a specific account. Read get_budget Get detailed information about a specific budget including accounts, categories, and settings. Read get_category Get detailed information about a specific category including current month data. Read get_history_entry Get detailed information about a specific history entry including before/after state. Read get_month Get detailed budget information for a specific month including all category balances. Read get_scheduled_transaction Get detailed information about a specific scheduled transaction. Read get_transaction Get detailed information about a specific transaction. Read list_accounts Get all accounts for a budget. Returns account names, types, balances, and status. Read list_budgets Get all budgets for the authenticated user. Returns budget names, IDs, and last modified dates. Read list_history List recent write operations with their IDs for undo. Operations are listed in reverse chronological order (ne Read list_months Get all budget months. Returns month summaries with income, budgeted, and activity totals. Read list_payees Get all payees for a budget. Read list_scheduled_transactions Get all scheduled/recurring transactions for a budget. Read list_transactions Get transactions for a budget. Supports filtering by date, type, category, payee, and account.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about YNAB MCP Server

Can an AI agent delete data through the YNAB MCP Server MCP server? +

Yes. The YNAB MCP Server server exposes 3 destructive tools including delete_scheduled_transaction, delete_transaction, undo_operation. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through YNAB MCP Server? +

The YNAB MCP Server server has 7 write tools including create_account, create_scheduled_transaction, create_transaction. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach YNAB MCP Server.

How many tools does the YNAB MCP Server MCP server expose? +

25 tools across 3 categories: Destructive, Read, Write. 15 are read-only. 10 can modify, create, or delete data.

How do I enforce a policy on YNAB MCP Server? +

Register the YNAB MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every YNAB MCP Server tool call.

Deterministic rules across all 25 YNAB MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON YNAB →

Instant setup, no code required.

25 YNAB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.