Get the most active switches in a site, sorted by traffic volume.
AI agents call getDashboardMostActiveSwitches to retrieve information from Tplink Omada without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access getDashboardMostActiveSwitches gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tplink Omada, and nothing reaches the server without passing your rules. This is the rule we recommend for getDashboardMostActiveSwitches:
{
"version": "1",
"default": "deny",
"tools": {
"getDashboardMostActiveSwitches": {}
}
}getDashboardMostActiveSwitches is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the most active switches in a site, sorted by traffic volume. 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 getDashboardMostActiveSwitches: 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.
getDashboardMostActiveSwitches 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 getDashboardMostActiveSwitches 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 getDashboardMostActiveSwitches. 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.
getDashboardMostActiveSwitches 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.
Start from Tplink Omada, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
327 Tplink Omada tools catalogued and risk-classified — across an index of 43,000+ MCP servers.