nordvpn_status
Check NordVPN connection status: connected/disconnected, auto-connect, snooze, and last known location. Does NOT open NordVPN.
This record as markdown: /tools/com-local-mcp-local-mcp/nordvpn-status.md
What nordvpn_status does on Local
AI agents call nordvpn_status 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.
Why nordvpn_status is rated Low
This tool only reads and reports VPN status information—it does not modify settings, execute connections, or trigger VPN actions. The explicit statement 'Does NOT open NordVPN' reinforces that it is a passive query tool. No data is written, deleted, or external actions triggered based on arguments. It is a straightforward information retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'Check[s] NordVPN connection status: connected/disconnected, auto-connect, snooze, and last known location.' The verb 'check' and the focus on querying status information indicates data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs nordvpn_status 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_status, this is the rule to start with:
nordvpn_status is read-only, so it stays allowed. 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 nordvpn_status call is checked against it from then on.
Questions about nordvpn_status
Check NordVPN connection status: connected/disconnected, auto-connect, snooze, and last known location. Does NOT open NordVPN. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
Register the Local MCP server in PolicyLayer and add a rule for nordvpn_status: 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.
nordvpn_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the nordvpn_status 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 nordvpn_status. 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.
nordvpn_status 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