actual_transactions_delete
Delete a transaction from Actual Budget by its ID.
This record as markdown: /tools/actual/actual-transactions-delete.md
What actual_transactions_delete does on Actual
AI agents call actual_transactions_delete to permanently remove resources in Actual, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why actual_transactions_delete is rated Critical
Deleting a transaction is a destructive operation that cannot be undone and permanently alters financial records in the system. Even though it operates on a single transaction rather than bulk data, the irreversible nature of deletion and the financial context (Actual Budget) justify the Destructive category with high severity.
From the tool's definition Tool name contains 'delete' and description states 'Delete a transaction from Actual Budget by its ID.' This irreversibly removes a financial record.
Attacks that exploit this kind of access
The rule that runs actual_transactions_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Actual, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For actual_transactions_delete, this is the rule to start with:
actual_transactions_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Actual, apply this rule, and every actual_transactions_delete call is checked against it from then on.
Questions about actual_transactions_delete
Delete a transaction from Actual Budget by its ID. It is categorised as a Destructive tool in the Actual MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Actual MCP server in PolicyLayer and add a rule for actual_transactions_delete: 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 Actual. Nothing to install.
actual_transactions_delete 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 actual_transactions_delete 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 actual_transactions_delete. 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.
actual_transactions_delete is provided by the Actual MCP server (actual-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Actual, and thousands of servers like it.
Across the catalogue