[1 API call] Delete a scheduled transaction
AI agents call delete_scheduled_transaction to permanently remove resources in Ynab — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a scheduled transaction, which cannot be undone. While it operates on scheduled (not yet executed) transactions rather than posted transactions, deletion is still a destructive operation that removes financial planning data. Categorized as Destructive rather than Financial because the primary harm is data loss, though the financial domain raises severity from medium to high.
From the tool's definition Tool name is 'delete_scheduled_transaction' with description 'Delete a scheduled transaction'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
[1 API call] Delete a scheduled transaction. It is categorised as a Destructive tool in the Ynab MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ynab MCP server in PolicyLayer and add a rule for delete_scheduled_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. Nothing to install.
delete_scheduled_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_scheduled_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_scheduled_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_scheduled_transaction 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.
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 →