whatsapp_disconnect
Unlink WhatsApp from Local MCP — logs out the linked device on this Mac (via wacli). Your chats stay on your phone; this only disconnects this Mac, and WhatsApp tools stop working until you run whatsapp_connect again. Write operation: the first call (confirm=false) returns a preview without disco...
This record as markdown: /tools/com-local-mcp-local-mcp/whatsapp-disconnect.md
What whatsapp_disconnect does on Local
AI agents use whatsapp_disconnect to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
confirm | boolean | — | Must be true to actually unlink. Without it, returns a preview. |
Parameters from the server's own tool schema.
Why whatsapp_disconnect is rated Medium
Unlinking WhatsApp is a reversible write operation that modifies the authentication state of the Mac device. While it disconnects the service, it does not delete data ('Your chats stay on your phone') and can be undone by calling whatsapp_connect again. This makes it Write rather than Destructive.
From the tool's definition The tool performs 'Unlink WhatsApp' and 'logs out the linked device' with a confirmation pattern. The description explicitly states 'Write operation: the first call (confirm=false) returns a preview without disconnecting; set confirm=true to actually unlink.'…
Attacks that exploit this kind of access
The rule that runs whatsapp_disconnect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For whatsapp_disconnect, this is the rule to start with:
whatsapp_disconnect stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every whatsapp_disconnect call is checked against it from then on.
Questions about whatsapp_disconnect
Unlink WhatsApp from Local MCP — logs out the linked device on this Mac (via wacli). Your chats stay on your phone; this only disconnects this Mac, and WhatsApp tools stop working until you run whatsapp_connect again. Write operation: the first call (confirm=false) returns a preview without disconnecting; set confirm=true to actually unlink. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
whatsapp_disconnect accepts 1 parameter: confirm. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for whatsapp_disconnect: 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 Local. Nothing to install.
whatsapp_disconnect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the whatsapp_disconnect 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_disconnect. 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_disconnect is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue