connect_instance · Evolution API WhatsApp MCP Server MCP

WHAT IT DOES

What connect_instance does on Evolution API WhatsApp MCP Server

AI agents invoke connect_instance to trigger actions in Evolution API WhatsApp MCP Server. 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 IT NEEDS A POLICY

Why connect_instance needs a policy

Connecting a WhatsApp instance triggers an external operation that establishes a live connection to WhatsApp's infrastructure. This is not a simple read or write — it initiates an active session/integration with external services, which can have broad operational impact (e.g., enabling message sending capabilities, tying a phone number to a session).

From the tool's definition Connect a WhatsApp instance

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_instance Rate-limited

connect_instance 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": {
    "connect_instance": {
      "limits": [
        {
          "counter": "connect_instance_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Evolution API WhatsApp MCP Server, so you can run agents against it safely.

FAQ

Questions about connect_instance

What does the connect_instance tool do? +

Connect a WhatsApp instance. It is categorised as a Execute tool in the Evolution API WhatsApp MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on connect_instance? +

Register the Evolution API WhatsApp MCP Server MCP server in PolicyLayer and add a rule for connect_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 Evolution API WhatsApp MCP Server. Nothing to install.

What risk level is connect_instance? +

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

Can I rate-limit connect_instance? +

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

How do I block connect_instance completely? +

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

What MCP server provides connect_instance? +

connect_instance is provided by the Evolution API WhatsApp MCP Server MCP server (luiso2/mcp-evolution-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.