Permanently delete a journal entry and its postings (used to correct mistakes or remove duplicate imports). Returns what was deleted. This cannot be undone.
AI agents call delete_transaction to permanently remove resources in Bookie — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes accounting journal entries and their postings without recovery. Even though it is used for legitimate corrections, the irreversible nature of the action and the critical importance of financial records for compliance and auditability make this a Destructive-category operation.
From the tool's definition Tool description explicitly states: 'Permanently delete a journal entry and its postings' and 'This cannot be undone.' These exact phrases indicate irreversible deletion of financial accounting records.
Attacks that exploit this kind of access
Permanently delete a journal entry and its postings (used to correct mistakes or remove duplicate imports). Returns what was deleted. This cannot be undone. It is categorised as a Destructive tool in the Bookie MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bookie 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 Bookie. 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 Bookie MCP server (yuens1002/bookie). 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 →