nordvpn_servers
Get recommended NordVPN servers by country or specialty. Uses NordVPN public API (no account needed). Returns server name, hostname, country, city, load %, and supported technologies.
This record as markdown: /tools/com-local-mcp-local-mcp/nordvpn-servers.md
What nordvpn_servers does on Local
AI agents call nordvpn_servers 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Server type filter: 'standard', 'p2p', 'double_vpn', 'onion', 'dedicated_ip'. Default: standard. |
limit | integer | — | Number of servers to return (1-10). Default: 5. |
country | string | — | Country name or 2-letter code (e.g. 'US', 'United States', 'JP'). Omit for auto-recommendation. |
Parameters from the server's own tool schema.
Why nordvpn_servers is rated Low
This tool only retrieves and returns information about NordVPN server recommendations and their properties. It does not create, modify, delete, execute code, trigger external operations, or move money. The public API query has no persistent effects on any system. Severity is low because misuse would only result in information retrieval about VPN servers, with no harmful blast radius.
From the tool's definition Tool description states it "Get[s] recommended NordVPN servers" and "Returns server name, hostname, country, city, load %, and supported technologies." This is purely a query/retrieval operation against a public API with no side effects.
Attacks that exploit this kind of access
The rule that runs nordvpn_servers 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_servers, this is the rule to start with:
nordvpn_servers 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_servers call is checked against it from then on.
Questions about nordvpn_servers
Get recommended NordVPN servers by country or specialty. Uses NordVPN public API (no account needed). Returns server name, hostname, country, city, load %, and supported technologies. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
nordvpn_servers accepts 3 parameters: type, limit, country. 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 nordvpn_servers: 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_servers 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_servers 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_servers. 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_servers 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