zalo_send_message

Sends a Zalo message to a conversation. WRITE operation with a preview gate: the first call (confirm=false) returns a preview WITHOUT sending; set confirm=true to actually send. to is a thread id from zalo_list_chats; set type="group" for a group.

SERVERLocal SOURCElocal-mcp
Medium RISK CLASS
Category Write
Parameters 42 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-send-message.md

What zalo_send_message does on Local

AI agents use zalo_send_message to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.

ParameterTypeRequiredDescription
to string Yes Thread id (from zalo_list_chats).
type string "user" (default) or "group".
confirm boolean Must be true to actually send. Without it, returns a preview.
message string Yes Text to send.

Parameters from the server's own tool schema.

Why zalo_send_message is rated Medium

This tool creates/sends a new message, which modifies state in Zalo (a messaging platform). It is reversible in that messages can typically be deleted after sending. The confirm=false preview mechanism reduces immediate risk of accidental sends.

From the tool's definition 'Sends a Zalo message to a conversation. WRITE operation' — explicitly labeled as WRITE. Has a confirm gate to preview before sending.

Questions about zalo_send_message

What does the zalo_send_message tool do? +

Sends a Zalo message to a conversation. WRITE operation with a preview gate: the first call (confirm=false) returns a preview WITHOUT sending; set confirm=true to actually send. to is a thread id from zalo_list_chats; set type="group" for a group. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does zalo_send_message accept? +

zalo_send_message accepts 4 parameters: to, type, confirm, message. Required: to, message. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on zalo_send_message? +

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

zalo_send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit zalo_send_message? +

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

Set action: deny in the PolicyLayer policy for zalo_send_message. 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_send_message? +

zalo_send_message 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Local's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.