Delete a chat.
AI agents call whatsapp_delete_chat to permanently remove resources in WSAPI WhatsApp 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 conversation history and cannot be undone. This is a destructive action that permanently eliminates data. While the blast radius is somewhat contained to a single chat rather than account-wide, the data loss is complete and unrecoverable, warranting 'Destructive' category and 'high' severity for an AI agent that could accidentally delete important conversations.
From the tool's definition Tool name is 'whatsapp_delete_chat' with description 'Delete a chat.' The verb 'delete' indicates irreversible removal of data (chat history and associated messages).
Attacks that exploit this kind of access
Delete a chat. It is categorised as a Destructive tool in the WSAPI WhatsApp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WSAPI WhatsApp MCP Server MCP server in PolicyLayer and add a rule for whatsapp_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 WSAPI WhatsApp MCP Server. Nothing to install.
whatsapp_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 whatsapp_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 whatsapp_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.
whatsapp_delete_chat is provided by the WSAPI WhatsApp MCP Server MCP server (wsapi-chat/wsapi-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 →