zalo_diagnose

Reports whether Zalo is linked to Local MCP (via zalo_connect). Call it first if Zalo tools aren't working.

SERVERLocal SOURCElocal-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/zalo-diagnose.md

WHAT IT DOES

What zalo_diagnose does on Local

AI agents call zalo_diagnose 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.

RISK

Why zalo_diagnose is rated Low

This tool queries the state of a Zalo connection and returns diagnostic information. It does not create, modify, delete, or execute operations—it merely retrieves and reports connection status. This is a read-only diagnostic operation with no blast radius if misused by an AI agent, as it cannot cause harm through incorrect invocation.

From the tool's definition Tool name and description indicate it 'Reports whether Zalo is linked' and performs diagnostic checks. The verb 'Reports' and phrase 'Call it first if Zalo tools aren't working' indicate a diagnostic/status-checking function with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zalo_diagnose 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_diagnose, this is the rule to start with:

zalo_diagnose Allowed

zalo_diagnose is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zalo_diagnose": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every zalo_diagnose call is checked against it from then on.

FAQ

Questions about zalo_diagnose

What does the zalo_diagnose tool do? +

Reports whether Zalo is linked to Local MCP (via zalo_connect). Call it first if Zalo tools aren't working. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zalo_diagnose? +

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

zalo_diagnose is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zalo_diagnose? +

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

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

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

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →