whatsapp_connect

SERVERLocal SOURCElocal-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/whatsapp-connect.md

WHAT IT DOES

What whatsapp_connect does on Local

AI agents invoke whatsapp_connect to trigger actions in Local. 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.

RISK

Why whatsapp_connect is rated High

The tool initiates an external authentication/linking session with WhatsApp by generating and displaying a QR code, then establishes a persistent connected session. This triggers an external operation (device linking) whose effects persist beyond the call. It's not purely Read or Write — it executes a session establishment flow that enables subsequent messaging tools.

From the tool's definition 'Link WhatsApp to Local MCP by showing a QR code right here in the chat', 'triggers external operations' — initiates a WhatsApp session linking process and activates external WhatsApp tools

Attacks that exploit this kind of access

RECOMMENDED RULE

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

whatsapp_connect Rate-limited

whatsapp_connect stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every whatsapp_connect call is checked against it from then on.

FAQ

Questions about whatsapp_connect

What does the whatsapp_connect tool do? +

Link WhatsApp to Local MCP by showing a QR code right here in the chat — no Terminal needed. Call this, then on your phone open WhatsApp → Settings → Linked Devices → Link a Device, and scan the QR shown. After you scan, WhatsApp tools (whatsapp_list_chats, whatsapp_read_messages, …) start working. If WhatsApp is already linked, it just reports that. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on whatsapp_connect? +

Register the Local MCP server in PolicyLayer and add a rule for whatsapp_connect: 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.

What risk level is whatsapp_connect? +

whatsapp_connect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit whatsapp_connect? +

Yes. Add a rate_limit block to the whatsapp_connect 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.

How do I block whatsapp_connect completely? +

Set action: deny in the PolicyLayer policy for whatsapp_connect. 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.

What MCP server provides whatsapp_connect? +

whatsapp_connect 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.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools → High-risk tools on this server →

Across the catalogue

adb_connect_device on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →