getLanClientCount

What getLanClientCount does on Tplink Omada

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

This tool retrieves statistics about client distribution across different LAN segments. It performs a read-only query of existing data with no capacity to modify, delete, or execute commands. The low severity reflects minimal blast radius—an AI agent misusing this would only access informational data about network client counts, not sensitive authentication credentials or ability to alter network configuration.

From the tool's definition Tool name 'getLanClientCount' and description 'Get client distribution breakdown across LAN segments' indicate a retrieval operation that queries existing data without modification or side effects.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getLanClientCount": {}
  }
}

Questions about getLanClientCount