wa_restart_instance

What wa_restart_instance does on WA MCP

AI agents invoke wa_restart_instance to trigger actions in WA MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why wa_restart_instance is rated High

This tool runs code that manages WhatsApp instance lifecycle (disconnect/reconnect operations). While not destructive (reversible) or write-based (doesn't create/modify persistent data), it executes external operations with side effects that depend on arguments. The medium severity reflects that misuse could disrupt messaging access but lacks financial or irreversible consequences.

From the tool's definition Tool performs 'Disconnect and reconnect a WhatsApp instance' — a system-level operation that triggers external service calls and state changes. The tool executes connection/disconnection logic whose effects depend on which instance is targeted.

The rule that runs wa_restart_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_restart_instance, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wa_restart_instance": {
      "limits": [
        {
          "counter": "wa_restart_instance_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about wa_restart_instance