Delete a customer by ID. DELETE /customers/{customerId}. WARNING: Cascading delete may remove or orphan related data (addresses, payment methods, subscriptions, invoices, etc.). Use with caution.
AI agents call delete_customer to permanently remove resources in Rebillia MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes customer records and cascades to remove or orphan related data across multiple entities. Deletion is irreversible and affects billing records, subscriptions, and payment information. The cascading nature and warning language confirm this cannot be undone.
From the tool's definition Tool name is 'delete_customer' and description explicitly states 'Delete a customer by ID' with 'DELETE /customers/{customerId}'. Warning states 'Cascading delete may remove or orphan related data (addresses, payment methods, subscriptions, invoices, etc.)'
Attacks that exploit this kind of access
Delete a customer by ID. DELETE /customers/{customerId}. WARNING: Cascading delete may remove or orphan related data (addresses, payment methods, subscriptions, invoices, etc.). Use with caution. It is categorised as a Destructive tool in the Rebillia MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rebillia 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 Rebillia 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 Rebillia MCP Server MCP server (rhinosaas/rebillia-mcp-server). 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 →