listDevices

List all provisioned (adopted) network devices in a site: gateways, switches, and access points. Returns MAC address, model, firmware version, IP, uptime, CPU/memory usage, and status for each device. Use MAC addresses from this response as input to getGatewayDetail, getSwitchDetail, getApDetail,...

SERVERTplink Omada SOURCEmigueltvms/tplink-omada-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/migueltvms-tplink-omada-mcp/listdevices.md

WHAT IT DOES

What listDevices does on Tplink Omada

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

RISK

Why listDevices is rated Low

The tool retrieves and queries device information from the TP-Link Omada controller without performing any modifications, deletions, or code execution. It is a pure data retrieval function that returns static device metadata.

From the tool's definition Tool name is 'listDevices' and description explicitly states it 'List[s] all provisioned (adopted) network devices in a site' and 'Returns MAC address, model, firmware version, IP, uptime, CPU/memory usage, and status'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs listDevices safely

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

listDevices Allowed

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

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

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

FAQ

Questions about listDevices

What does the listDevices tool do? +

How do I enforce a policy on listDevices? +

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

What risk level is listDevices? +

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

Can I rate-limit listDevices? +

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

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

listDevices is provided by the Tplink Omada MCP server (migueltvms/tplink-omada-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tplink Omada, and thousands of servers like it.

This server

All 327 Tplink Omada tools →

Across the catalogue

The MCP Attack Database →

Guides

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