wa_delete_instance
Permanently delete a WhatsApp instance and all its data including auth state, messages, contacts, and queue. This action cannot be undone.
This record as markdown: /tools/delltrak-wamcp/wa-delete-instance.md
What wa_delete_instance does on WA MCP
AI agents call wa_delete_instance to permanently remove resources in WA MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why wa_delete_instance is rated Critical
This tool irreversibly deletes substantial amounts of data (auth state, messages, contacts, queue) with no recovery mechanism. The explicit 'cannot be undone' language and 'permanently delete' phrasing confirm it is destructive. The blast radius is critical because deletion of authentication state and all messages could compromise user accounts and permanently erase communication history.
From the tool's definition Tool description explicitly states: 'Permanently delete a WhatsApp instance and all its data including auth state, messages, contacts, and queue. This action cannot be undone.'
Attacks that exploit this kind of access
The rule that runs wa_delete_instance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WA MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wa_delete_instance, this is the rule to start with:
wa_delete_instance is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect WA MCP, apply this rule, and every wa_delete_instance call is checked against it from then on.
Questions about wa_delete_instance
Permanently delete a WhatsApp instance and all its data including auth state, messages, contacts, and queue. This action cannot be undone. It is categorised as a Destructive tool in the WA MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WA MCP server in PolicyLayer and add a rule for wa_delete_instance: 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 WA MCP. Nothing to install.
wa_delete_instance 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 wa_delete_instance 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 wa_delete_instance. 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.
wa_delete_instance is provided by the WA MCP server (delltrak/wamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WA, and thousands of servers like it.
Across the catalogue