nordvpn_diagnose

Run a diagnostic check on NordVPN: installation, login state, connection status, kill switch, and supported protocols. Useful for troubleshooting.

SERVERLocal SOURCElocal-mcp

High RISK CLASS

Category Execute

Parameters 00 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/nordvpn-diagnose.md

WHAT IT DOES

What nordvpn_diagnose does on Local

AI agents invoke nordvpn_diagnose to trigger actions in Local. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why nordvpn_diagnose is rated High

This tool executes an external operation (diagnostic check) that queries system state and NordVPN status, which fits the Execute category for triggering external operations whose effects depend on arguments/state. Severity is low because diagnostics are informational-only with no data modification, deletion, or financial impact; worst case is temporary system interaction to gather status information.

From the tool's definition Tool name 'nordvpn_diagnose' and description 'Run a diagnostic check on NordVPN: installation, login state, connection status, kill switch, and supported protocols' indicate execution of a diagnostic command against the NordVPN system.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

nordvpn_diagnose Rate-limited

nordvpn_diagnose stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nordvpn_diagnose": {
      "limits": [
        {
          "counter": "nordvpn_diagnose_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about nordvpn_diagnose

What does the nordvpn_diagnose tool do? +

Run a diagnostic check on NordVPN: installation, login state, connection status, kill switch, and supported protocols. Useful for troubleshooting. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on nordvpn_diagnose? +

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

nordvpn_diagnose is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit nordvpn_diagnose? +

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

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

nordvpn_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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →