delete_transaction

Delete a transaction by its ID. This action cannot be undone.

Server Actual Budget MCP Server yhc0712/actual-budget-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_transaction does on Actual Budget MCP Server

AI agents call delete_transaction to permanently remove resources in Actual Budget MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_transaction needs a policy

Deleting a transaction in a financial management system is an irreversible action that permanently removes financial records. This meets the definition of Destructive (irreversibly deletes or overwrites data, or actions that cannot be undone). While it operates on financial data, the primary concern is the permanent data loss rather than money movement, so Destructive is more severe than Financial in this context.

From the tool's definition Tool description states: 'Delete a transaction by its ID. This action cannot be undone.' The word 'Delete' combined with explicit warning that the action is irreversible clearly indicates a destructive operation.

Questions about delete_transaction

What does the delete_transaction tool do? +

Delete a transaction by its ID. This action cannot be undone. It is categorised as a Destructive tool in the Actual Budget MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_transaction? +

Register the Actual Budget 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 Actual Budget MCP Server. Nothing to install.

What risk level is delete_transaction? +

delete_transaction is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_transaction? +

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.

How do I block delete_transaction completely? +

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.

What MCP server provides delete_transaction? +

delete_transaction is provided by the Actual Budget MCP Server MCP server (yhc0712/actual-budget-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.