Delete an entire chat conversation. This is irreversible.
AI agents call delete_chat to permanently remove resources in Bluebubbles — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes an entire chat conversation, which is the defining characteristic of the Destructive category. The description explicitly states 'irreversible', confirming the action cannot be undone. While the blast radius is scoped to a single chat rather than system-wide data, the permanent loss of communication history could have significant consequences for the user.
From the tool's definition 'Delete an entire chat conversation. This is irreversible.' - the tool permanently removes data with no undo capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete an entire chat conversation. This is irreversible. It is categorised as a Destructive tool in the Bluebubbles MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bluebubbles MCP server in PolicyLayer and add a rule for delete_chat: 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 Bluebubbles. Nothing to install.
delete_chat 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_chat 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_chat. 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_chat is provided by the Bluebubbles MCP server (metaember/bluebubbles-mcp). 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 →