Delete a message by ID. Use everyone=true to try deleting for everyone when supported.
AI agents call whatsapp_delete_message to permanently remove resources in Wappmcp — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call whatsapp_delete_message doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Wappmcp is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Delete a message by ID. Use everyone=true to try deleting for everyone when supported. It is categorised as a Destructive tool in the Wappmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Wapp MCP server in PolicyLayer and add a rule for whatsapp_delete_message: 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 Wappmcp. Nothing to install.
whatsapp_delete_message 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_message 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_message. 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_message is provided by the Wapp MCP server (wappmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.