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.
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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.
Attacks that exploit this kind of access
The rule that runs zalo_disconnect 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_disconnect, this is the rule to start with:
zalo_disconnect stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_disconnect call is checked against it from then on.
Questions about 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. 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.
zalo_disconnect accepts 1 parameter: confirm. 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_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.
zalo_disconnect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
This server
Across the catalogue