zalo_disconnect

Unlink Zalo from Local MCP (removes the saved session on this Mac). Your chats stay in Zalo; this only disconnects this Mac, and Zalo tools stop working until you run zalo_connect again. Write operation: first call (confirm=false) previews; confirm=true unlinks.

SERVERLocal SOURCElocal-mcp
Medium RISK CLASS
Category Write
Parameters 10 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-disconnect.md

What zalo_disconnect does on Local

AI agents use zalo_disconnect 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
confirm boolean Must be true to actually unlink.

Parameters from the server's own tool schema.

Why zalo_disconnect is rated Medium

This tool modifies system state by removing a saved session/credential configuration, which is a reversible write operation (can be undone by calling zalo_connect again). It does not delete user data in Zalo ('Your chats stay in Zalo'), only disconnects the local integration. The two-step confirmation pattern (preview then confirm) indicates a deliberate write action.

From the tool's definition Tool description explicitly states 'Write operation: first call (confirm=false) previews; confirm=true unlinks' and 'removes the saved session on this Mac'. The unlink operation modifies the local configuration by removing stored credentials/session.

Questions about zalo_disconnect

What does the zalo_disconnect tool do? +

Unlink Zalo from Local MCP (removes the saved session on this Mac). Your chats stay in Zalo; this only disconnects this Mac, and Zalo tools stop working until you run zalo_connect again. Write operation: first call (confirm=false) previews; confirm=true unlinks. 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_disconnect accept? +

zalo_disconnect accepts 1 parameter: confirm. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on zalo_disconnect? +

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

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

Can I rate-limit zalo_disconnect? +

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

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

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

Across the catalogue

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