Delete a chat completely. WARNING: This is a destructive operation that cannot be undone.
AI agents call waha_delete_chat to permanently remove resources in WAHA MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a chat irreversibly removes an entire conversation thread and its history. This is an irrevocable operation with no undo capability, fitting the Destructive category definition. While not a financial operation, the loss of communication history could have significant business or personal consequences.
From the tool's definition Tool name explicitly states 'delete_chat'; description states 'Delete a chat completely' with explicit warning 'This is a destructive operation that cannot be undone.'
Documented attack patterns abuse exactly the kind of access waha_delete_chat gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WAHA MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for waha_delete_chat:
{
"version": "1",
"default": "deny",
"hide": [
"waha_delete_chat"
]
} waha_delete_chat 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 a chat completely. WARNING: This is a destructive operation that cannot be undone. It is categorised as a Destructive tool in the WAHA MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WAHA MCP Server MCP server in PolicyLayer and add a rule for waha_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 WAHA MCP Server. Nothing to install.
waha_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 waha_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 waha_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.
waha_delete_chat is provided by the WAHA MCP Server MCP server (seejux/waha-whatsapp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WAHA 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.
52 WAHA MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.