Delete (make inactive) a customer in QuickBooks Online.
AI agents call delete_customer to permanently remove resources in QuickBooks Online MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting or making a customer inactive is a destructive operation that cannot be easily undone and represents a permanent change to business-critical data. This falls squarely into the Destructive category per the rules. While marked 'make inactive' (suggesting it may be reversible), the primary verb is 'delete' and the effect removes the customer from active use.
From the tool's definition Tool name is 'delete_customer' and description states 'Delete (make inactive) a customer in QuickBooks Online.' The use of 'Delete' in both the name and description indicates an irreversible or semi-irreversible action that removes or deactivates a customer…
Documented attack patterns abuse exactly the kind of access delete_customer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QuickBooks Online MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_customer:
{
"version": "1",
"default": "deny",
"hide": [
"delete_customer"
]
}delete_customer 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 (make inactive) a customer in QuickBooks Online. It is categorised as a Destructive tool in the QuickBooks Online MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the QuickBooks Online MCP Server MCP server in PolicyLayer and add a rule for delete_customer: 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 QuickBooks Online MCP Server. Nothing to install.
delete_customer 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_customer 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_customer. 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_customer is provided by the QuickBooks Online MCP Server MCP server (librechat-ai/quickbooks-online-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from QuickBooks Online MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
55 QuickBooks Online MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.