Delete a transaction by its ID. This action is permanent and cannot be undone.
AI agents call delete-transaction 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.
The tool permanently and irreversibly deletes financial transaction records with no undo capability. This is a core Destructive operation. Severity is high because accidental or malicious deletion of transaction history could corrupt financial records, disrupt budgeting accuracy, and require manual recovery efforts. The financial domain (Actual Budget) elevates the impact of data loss.
From the tool's definition "Delete a transaction by its ID. This action is permanent and cannot be undone." — explicitly irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access delete-transaction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Actual, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-transaction:
{
"version": "1",
"default": "deny",
"hide": [
"delete-transaction"
]
}delete-transaction disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a transaction by its ID. This action is permanent and cannot be undone. 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 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 Actual. 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 Actual MCP server (s-stefanov/actual-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Actual tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
25 Actual tools catalogued and risk-classified — across an index of 42,500+ MCP servers.