getDashboardMostActiveSwitches

What getDashboardMostActiveSwitches does on Tplink Omada

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

This tool queries existing network metrics to provide visibility into switch performance. While it accesses network infrastructure data, it performs no configuration changes, no commands are executed on devices, and no data is modified. The blast radius if misused by an agent is minimal—the worst case would be information disclosure about network topology and traffic patterns, which is a read-level concern.

From the tool's definition The tool retrieves 'the most active switches in a site, sorted by traffic volume.' The verb 'get' and the query nature of the operation ('sorted by traffic volume') indicate this is a read-only data retrieval operation with no modification or side effects.

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

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

Questions about getDashboardMostActiveSwitches