Delete a QBO entity by type and ID. Transactions (Invoice, Bill, JournalEntry, Payment, Purchase, Transfer, etc.) with a TxnDate on or before the company
AI agents call qbo_delete_entity to permanently remove resources in Kaizen Qbo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes financial data in QuickBooks Online, which cannot be undone and has severe business impact. Deletion of transactions, invoices, bills, and journal entries represents destruction of critical financial records. Even though it also interfaces with a financial system, the primary risk is the destructive/irreversible nature of the operation, making Destructive the most appropriate category.
From the tool's definition Tool name 'qbo_delete_entity' combined with description 'Delete a QBO entity by type and ID' indicates permanent deletion of QuickBooks Online records including financial transactions (Invoice, Bill, JournalEntry, Payment, Purchase, Transfer).
Attacks that exploit this kind of access
Delete a QBO entity by type and ID. Transactions (Invoice, Bill, JournalEntry, Payment, Purchase, Transfer, etc.) with a TxnDate on or before the company. It is categorised as a Destructive tool in the Kaizen Qbo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kaizen Qbo MCP server in PolicyLayer and add a rule for qbo_delete_entity: 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 Kaizen Qbo. Nothing to install.
qbo_delete_entity 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 qbo_delete_entity 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 qbo_delete_entity. 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.
qbo_delete_entity is provided by the Kaizen Qbo MCP server (kaizen-qbo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
qbo_delete_entity is one line of Kaizen Qbo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →