zalo_read_messages
Reads recent Zalo messages that Local MCP captured while linked. Optionally pass thread (a thread id from zalo_list_chats) to read one conversation. NOTE: Zalo's web protocol can't backfill old history — this returns messages received since Local MCP started listening (right after zalo_connect). ...
This record as markdown: /tools/com-local-mcp-local-mcp/zalo-read-messages.md
What zalo_read_messages does on Local
AI agents call zalo_read_messages 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 messages to return (default 50). |
thread | string | — | Thread id (from zalo_list_chats) to filter to one conversation; omit for all. |
Parameters from the server's own tool schema.
Why zalo_read_messages is rated Low
This tool retrieves message data from Zalo conversations without modifying, deleting, or executing any operations. While message access could be privacy-sensitive in a multi-user context, the tool itself performs only read operations.
From the tool's definition The tool description explicitly states it 'Reads recent Zalo messages' and provides a way to retrieve a specific conversation by passing a thread id from zalo_list_chats.
Attacks that exploit this kind of access
The rule that runs zalo_read_messages 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_read_messages, this is the rule to start with:
zalo_read_messages 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_read_messages call is checked against it from then on.
Questions about zalo_read_messages
Reads recent Zalo messages that Local MCP captured while linked. Optionally pass thread (a thread id from zalo_list_chats) to read one conversation. NOTE: Zalo's web protocol can't backfill old history — this returns messages received since Local MCP started listening (right after zalo_connect). Requires Zalo linked; otherwise returns an actionable connect hint, never a silent empty. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
zalo_read_messages accepts 2 parameters: limit, thread. 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_read_messages: 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_read_messages 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_read_messages 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_read_messages. 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_read_messages 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