Delete an existing transaction.
AI agents call delete_transaction to permanently remove resources in YNAB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes transaction records from a financial management system. Deletion of transactions is irreversible and could result in loss of financial history, incorrect account balances, and audit trail corruption. While not directly moving money (Financial category), the destruction of financial records has severe implications for data integrity and financial accountability.
From the tool's definition Tool name 'delete_transaction' combined with description 'Delete an existing transaction' explicitly indicates irreversible removal of financial data. The verb 'delete' is characteristic of destructive operations that cannot be undone.
Attacks that exploit this kind of access
Delete an existing transaction. It is categorised as a Destructive tool in the YNAB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the YNAB MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_transaction is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_transaction 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 →