Create a new transaction. Use negative amounts for spending, positive for income.
AI agents use ynab_create_transaction to create or update resources in YNAB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your YNAB MCP Server environment.
This tool creates new transaction records in a financial management system (YNAB), which modifies financial data reversibly. It does not move money between accounts (that is ynab_move_money), nor does it delete data (Destructive), nor does it directly process payments or financial obligations (Financial category reserved for actual money transfer, payments, trades, subscriptions).
From the tool's definition Tool name 'ynab_create_transaction' and description 'Create a new transaction' indicate the creation of new financial records.
Attacks that exploit this kind of access
Create a new transaction. Use negative amounts for spending, positive for income. It is categorised as a Write tool in the YNAB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the YNAB MCP Server MCP server in PolicyLayer and add a rule for ynab_create_transaction: 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_create_transaction is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ynab_create_transaction 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_create_transaction. 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_create_transaction 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 →