get_tunnel_diagnostics

SERVERMeridian SOURCE@meridianmcp/mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/get-tunnel-diagnostics.md

WHAT IT DOES

What get_tunnel_diagnostics does on Meridian

AI agents call get_tunnel_diagnostics to retrieve information from Meridian 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
`hostname`	string	—	Optional: report only this machine's per-host config override instead of the per-tenant default (mirrors get_tunnel_plugins's ?hostname=).

Parameters from the server's own tool schema.

RISK

Why get_tunnel_diagnostics is rated Low

Even though get_tunnel_diagnostics only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts URL/endpoint input (hostname)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_tunnel_diagnostics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tunnel_diagnostics, this is the rule to start with:

get_tunnel_diagnostics Allowed

get_tunnel_diagnostics 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": {
    "get_tunnel_diagnostics": {}
  }
}

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

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

FAQ

Questions about get_tunnel_diagnostics

What does the get_tunnel_diagnostics tool do? +

[MAINTENANCE] f1e0df55 — Read-only: ONE layered diagnostic snapshot of your tunnel/connectors, separating what's SAVED in the dashboard from what's ACTUALLY running so a saved-but-not-yet-applied setting is never reported as active. Per slot (fs/code/extract/ppt/word/dc/docs/zotero/outputs/debug): dashboard_configured (persisted), process_active (live server-side socket), external_child_state (last client-reported lifecycle state), last_error, and exact remediation text — plus one of five distinct states: healthy, stale, degraded, quarantined, or restart_required (persisted config and observed runtime disagree). Also reports the server-side tool routing cache size, a config generation + manifest_hash fingerprint for drift detection, and whether a tools/list re-discovery is pending. Includes a run_id + timestamp for correlating with support requests. Tokens/credentials are redacted. Requires an authenticated hosted tenant (tunnel mode) — self-hosted callers with no tenant get an empty, unauthenticated-shaped snapshot. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does get_tunnel_diagnostics accept? +

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

How do I enforce a policy on get_tunnel_diagnostics? +

Register the Meridian MCP server in PolicyLayer and add a rule for get_tunnel_diagnostics: 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 Meridian. Nothing to install.

What risk level is get_tunnel_diagnostics? +

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

Can I rate-limit get_tunnel_diagnostics? +

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

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

get_tunnel_diagnostics is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meridian, and thousands of servers like it.

This server

All 175 Meridian tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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