listDevicesStats
Query statistics for global adopted devices with pagination and filtering. Supports fuzzy search by MAC address, name, model, or serial number, and filtering by tag or device series type (0: basic, 1: pro).
This record as markdown: /tools/migueltvms-tplink-omada-mcp/listdevicesstats.md
What listDevicesStats does on Tplink Omada
AI agents call listDevicesStats 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 listDevicesStats is rated Low
The listDevicesStats tool is a read-only query operation that retrieves and filters device statistics. It supports search and pagination but does not create, modify, delete, or execute any operations. The only action is data retrieval with no side effects, which is characteristic of the Read category. Severity is low because querying device statistics poses minimal risk even if misused by an AI agent.
From the tool's definition Tool performs 'Query statistics' on devices with 'pagination and filtering' and 'fuzzy search' capabilities. No modification, deletion, or execution of commands is described.
Attacks that exploit this kind of access
The rule that runs listDevicesStats 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 listDevicesStats, this is the rule to start with:
listDevicesStats 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 listDevicesStats call is checked against it from then on.
Questions about listDevicesStats
Query statistics for global adopted devices with pagination and filtering. Supports fuzzy search by MAC address, name, model, or serial number, and filtering by tag or device series type (0: basic, 1: pro). 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 listDevicesStats: 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.
listDevicesStats 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 listDevicesStats 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 listDevicesStats. 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.
listDevicesStats 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