listMostActiveClients
Get the most active clients in a site, sorted by total traffic. Returns client name, MAC address, type, model, wireless status, and total traffic. This is a dashboard endpoint that provides a quick overview of top clients by traffic usage.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/listmostactiveclients.md
What listMostActiveClients does on Tplink Omada
AI agents call listMostActiveClients 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.
Why listMostActiveClients is rated Low
This is purely a data query operation that returns client statistics for monitoring/observability purposes. The description explicitly states it 'provides a quick overview' without side effects. No data is created, modified, deleted, or external operations triggered.
From the tool's definition Tool retrieves dashboard data ('Get the most active clients') with no modification, deletion, or execution capabilities. Returns read-only metrics: client name, MAC address, type, model, wireless status, and total traffic.
Attacks that exploit this kind of access
The rule that runs listMostActiveClients 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 listMostActiveClients, this is the rule to start with:
listMostActiveClients 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 Tplink Omada, apply this rule, and every listMostActiveClients call is checked against it from then on.
Questions about listMostActiveClients
Get the most active clients in a site, sorted by total traffic. Returns client name, MAC address, type, model, wireless status, and total traffic. This is a dashboard endpoint that provides a quick overview of top clients by traffic usage. It is categorised as a Read tool in the Tplink Omada MCP Server, which means it retrieves data without modifying state.
Register the Tplink Omada MCP server in PolicyLayer and add a rule for listMostActiveClients: 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.
listMostActiveClients 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 listMostActiveClients 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 listMostActiveClients. 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.
listMostActiveClients 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.
More on Tplink Omada, and thousands of servers like it.
This server
Across the catalogue