zalo_search_messages
Searches your captured Zalo messages by text. Searches only messages received while Local MCP was linked and listening (Zalo can't backfill older history). Requires Zalo linked; otherwise returns an actionable connect hint.
This record as markdown: /tools/com-local-mcp-local-mcp/zalo-search-messages.md
What zalo_search_messages does on Local
AI agents call zalo_search_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 matches to return (default 50). |
query | string | Yes | Text to search for in message content. |
Parameters from the server's own tool schema.
Why zalo_search_messages is rated Low
This tool retrieves and searches message data without any side effects. The operation is read-only, returning search results from an existing message store. While it accesses potentially sensitive message content, the capability itself is non-destructive and non-modifying. Severity is low because search operations have minimal blast radius—they cannot alter state, execute code, or cause data loss.
From the tool's definition Tool description states it 'Searches your captured Zalo messages by text' and 'Searches only messages received while Local MCP was linked' - these are query/search operations with no modification, creation, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs zalo_search_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_search_messages, this is the rule to start with:
zalo_search_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_search_messages call is checked against it from then on.
Questions about zalo_search_messages
Searches your captured Zalo messages by text. Searches only messages received while Local MCP was linked and listening (Zalo can't backfill older history). Requires Zalo linked; otherwise returns an actionable connect hint. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
zalo_search_messages accepts 2 parameters: limit, query. Required: query. 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_search_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_search_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_search_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_search_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_search_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