Low Risk

squads_accessible_nodes

Get nodes accessible to a specific squad

How to control squads_accessible_nodes ↓

AI agents call squads_accessible_nodes to retrieve information from Remnawave without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves information about which nodes are accessible to a squad—a read-only operation with no side effects. It queries existing configuration without creating, modifying, deleting, or executing operations. The low severity reflects that unauthorized access to this information would have limited direct impact compared to tools that could modify VPN configuration, delete data, or execute commands.

From the tool's definition Tool name 'squads_accessible_nodes' and description 'Get nodes accessible to a specific squad' indicate a query/retrieval operation with no modification of data.

Documented attack patterns abuse exactly the kind of access squads_accessible_nodes gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Remnawave, and nothing reaches the server without passing your rules. This is the rule we recommend for squads_accessible_nodes:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "squads_accessible_nodes": {}
  }
}

squads_accessible_nodes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Remnawave — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the squads_accessible_nodes tool do? +

Get nodes accessible to a specific squad. It is categorised as a Read tool in the Remnawave MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on squads_accessible_nodes? +

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

What risk level is squads_accessible_nodes? +

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

Can I rate-limit squads_accessible_nodes? +

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

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

squads_accessible_nodes is provided by the Remnawave MCP server (trackline/mcp-remnawave). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Remnawave tool call.

Deterministic rules across all 153 Remnawave tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

153 Remnawave tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.