zalo_list_chats
Lists your Zalo conversations — friends and groups — so you can pick a recipient. Requires Zalo linked (zalo_connect); if it isn't, returns an actionable connect hint, never an empty list.
This record as markdown: /tools/com-local-mcp-local-mcp/zalo-list-chats.md
What zalo_list_chats does on Local
AI agents call zalo_list_chats to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max friends to return (default 100). |
Parameters from the server's own tool schema.
Why zalo_list_chats is rated Low
This tool retrieves and displays existing chat metadata to enable selection. It has no capability to create, modify, delete, execute code, or transfer funds. The worst-case misuse (enumeration of chat contacts) has limited blast radius compared to Write/Execute/Destructive operations. Confidence is high because the description clearly indicates read-only retrieval behavior.
From the tool's definition Tool name 'zalo_list_chats' and description 'Lists your Zalo conversations' indicate a retrieval operation with no side effects. The phrase 'so you can pick a recipient' confirms it serves a query/browse purpose rather than executing actions or modifying data.
Attacks that exploit this kind of access
The rule that runs zalo_list_chats 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_list_chats, this is the rule to start with:
zalo_list_chats is read-only, so it stays allowed. 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 zalo_list_chats call is checked against it from then on.
Questions about zalo_list_chats
Lists your Zalo conversations — friends and groups — so you can pick a recipient. Requires Zalo linked (zalo_connect); if it isn't, returns an actionable connect hint, never an empty list. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
zalo_list_chats accepts 1 parameter: limit. 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 zalo_list_chats: 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.
zalo_list_chats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the zalo_list_chats 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 zalo_list_chats. 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.
zalo_list_chats 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