zalo_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/zalo-connect.md

WHAT IT DOES

What zalo_connect does on Local

AI agents invoke zalo_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 zalo_connect is rated High

This tool initiates an external session linkage with the Zalo messaging platform by generating and displaying a QR code, then establishing a live web session. It triggers an external operation (OAuth-like session binding) whose effects depend on user action and can displace existing sessions ('may end this one').

From the tool's definition 'Link Zalo to Local MCP by showing a QR code right here in the chat' and 'Zalo tools (zalo_list_chats, zalo_send_message) start working' — triggers an external authentication/session operation that enables further messaging capabilities

Attacks that exploit this kind of access

RECOMMENDED RULE

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

zalo_connect Rate-limited

zalo_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": {
    "zalo_connect": {
      "limits": [
        {
          "counter": "zalo_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 zalo_connect call is checked against it from then on.

FAQ

Questions about zalo_connect

What does the zalo_connect tool do? +

Link Zalo to Local MCP by showing a QR code right here in the chat. Call this, then on your phone open Zalo → the QR-scan option, and scan it. After you scan, Zalo tools (zalo_list_chats, zalo_send_message) start working. If Zalo is already linked, it says so. Zalo allows only ONE linked web session at a time — if Zalo Web / another device is open, it may end this one. 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 zalo_connect? +

Register the Local MCP server in PolicyLayer and add a rule for zalo_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 zalo_connect? +

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

Can I rate-limit zalo_connect? +

Yes. Add a rate_limit block to the zalo_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 zalo_connect completely? +

Set action: deny in the PolicyLayer policy for zalo_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 zalo_connect? +

zalo_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 →