node_list

List connected mobile companion devices (nodes). Returns information about each connected device including its capabilities and available commands.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/node-list.md

WHAT IT DOES

What node_list does on CoWork OS

AI agents call node_list to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why node_list is rated Low

This tool performs a query operation that retrieves metadata about connected devices. It returns informational data (device capabilities and available commands) without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal—an agent could only gain visibility into connected devices, not control or manipulate them.

From the tool's definition Tool name 'node_list' and description 'List connected mobile companion devices (nodes). Returns information about each connected device including its capabilities and available commands.' explicitly indicates data retrieval with no modification or side…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs node_list safely

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

node_list Allowed

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

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

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

FAQ

Questions about node_list

What does the node_list tool do? +

List connected mobile companion devices (nodes). Returns information about each connected device including its capabilities and available commands. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on node_list? +

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

What risk level is node_list? +

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

Can I rate-limit node_list? +

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

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

node_list is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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