Remove a transaction by txn_id; supports dry-run preview.
AI agents call remove_transaction to permanently remove resources in MCP Beancount Tool — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes financial records from a Beancount accounting ledger. Deletion of transactions is irreversible and undermines the fundamental principle of immutable audit logs in accounting systems. Even with dry-run capability, the actual removal operation causes permanent data loss.
From the tool's definition Tool performs irreversible deletion: 'Remove a transaction by txn_id'. Transactions in accounting ledgers are permanent records that cannot be undone once deleted; removal destroys audit trail integrity.
Attacks that exploit this kind of access
Remove a transaction by txn_id; supports dry-run preview. It is categorised as a Destructive tool in the MCP Beancount Tool MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Beancount Tool MCP server in PolicyLayer and add a rule for remove_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 MCP Beancount Tool. Nothing to install.
remove_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 remove_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 remove_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.
remove_transaction is provided by the MCP Beancount Tool MCP server (onesvat/mcp-beancount). 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 →