Delete a previously posted status update.
AI agents call whatsapp_delete_status 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.
The tool permanently removes a status update that cannot be recovered. While the blast radius is moderate (affects only the user's own status, not others' data or financial systems), the action is irreversible and represents data destruction. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.'
From the tool's definition Tool name contains 'delete' and description states 'Delete a previously posted status update' — this irreversibly removes user-generated content.
Attacks that exploit this kind of access
Delete a previously posted status update. 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_status: 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_status 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_status 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_status. 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_status 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 →