update_payee · Ynab MCP: Risk & Policy

WHAT IT DOES

What update_payee does on Ynab

AI agents use update_payee to create or update resources in Ynab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ynab environment.

WHY IT NEEDS A POLICY

Why update_payee needs a policy

This tool modifies payee records reversibly within a financial system, making it a Write operation rather than Read (data retrieval only) or Destructive (irreversible deletion). While it operates in a financial context, it does not move money, create financial obligations, or commit transactions—it only updates metadata about payee entities.

From the tool's definition Tool name 'update_payee' and description 'Update a payee' indicate modification of existing data. The context shows this is part of YNAB's financial management API where payees are entities used in transaction tracking and budgeting.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_payee Rate-limited

update_payee stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_payee": {
      "limits": [
        {
          "counter": "update_payee_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ynab, so you can run agents against it safely.

FAQ

Questions about update_payee

What does the update_payee tool do? +

[1 API call] Update a payee. It is categorised as a Write tool in the Ynab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_payee? +

Register the Ynab MCP server in PolicyLayer and add a rule for update_payee: 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. Nothing to install.

What risk level is update_payee? +

update_payee is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_payee? +

Yes. Add a rate_limit block to the update_payee 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.

How do I block update_payee completely? +

Set action: deny in the PolicyLayer policy for update_payee. 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.

What MCP server provides update_payee? +

update_payee is provided by the Ynab MCP server (justmytwospence/ynab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.