listClients

List all network clients (wired and wireless) connected to a site. Returns client details including MAC address, IP, hostname, connected device, SSID (for wireless), signal strength, download/upload traffic, and online status. Use this to audit connected devices or find a specific client by name ...

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/listclients.md

WHAT IT DOES

What listClients does on Tplink Omada

AI agents call listClients 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 listClients is rated Low

This is a read-only operation that queries and enumerates connected clients on a network. While the information exposed (MAC addresses, IPs, hostnames, traffic patterns) could enable reconnaissance or targeting of specific devices, the tool itself performs no destructive, write, execute, or financial action.

From the tool's definition Tool description explicitly states 'List all network clients' and 'Returns client details' — retrieves network visibility data without modification. No verbs indicating state changes (create, modify, delete, execute).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs listClients 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 listClients, this is the rule to start with:

listClients Allowed

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

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 listClients call is checked against it from then on.

FAQ

Questions about listClients

What does the listClients tool do? +

How do I enforce a policy on listClients? +

Register the Tplink Omada MCP server in PolicyLayer and add a rule for listClients: 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 listClients? +

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

Can I rate-limit listClients? +

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

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

listClients 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 →