# getDashboardMostActiveSwitches

Get the most active switches in a site, sorted by traffic volume.

Agent View of the PolicyLayer registry record for `getDashboardMostActiveSwitches`. HTML page: https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getdashboardmostactiveswitches

## Facts

- Tool: `getDashboardMostActiveSwitches`
- Server: Tplink Omada (`migueltvms/tplink-omada-mcp`) — https://policylayer.com/tools/migueltvms-tplink-omada-mcp.md
- Homepage: https://github.com/MiguelTVMS/tplink-omada-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "getDashboardMostActiveSwitches",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Tplink Omada:

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

## Other tools on Tplink Omada (326)

- `getAccessControl` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getaccesscontrol.md
- `getAclConfigTypeSetting` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getaclconfigtypesetting.md
- `getAdvancedVpnSetting` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getadvancedvpnsetting.md
- `getAlg` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getalg.md
- `getAllCloudUsers` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getallcloudusers.md
- `getAllDeviceBySite` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getalldevicebysite.md
- `getAllLocalUsers` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getalllocalusers.md
- `getAllRoles` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getallroles.md
- `getAllUsersApp` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getallusersapp.md
- `getApDetail` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getapdetail.md
- `getApGeneralConfig` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getapgeneralconfig.md
- `getApIpv6Config` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getapipv6config.md
- `getApLldpConfig` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getaplldpconfig.md
- `getApLoadBalance` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getaploadbalance.md
- `getApOfdmaConfig` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getapofdmaconfig.md
- `getAppControlCategories` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getappcontrolcategories.md
- `getAppControlRules` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getappcontrolrules.md
- `getAppGroupProfile` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getappgroupprofile.md
- `getApplicationAcl` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getapplicationacl.md
- `getApplicationControlStatus` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getapplicationcontrolstatus.md
- `getApQosConfig` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getapqosconfig.md
- `getApRadios` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getapradios.md
- `getApSnmpConfig` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getapsnmpconfig.md
- `getApUplinkConfig` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getapuplinkconfig.md
- `getApVlanConfig` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getapvlanconfig.md
- `getAttackDefenseSetting` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getattackdefensesetting.md
- `getAuditLogSettingForGlobal` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getauditlogsettingforglobal.md
- `getAuditLogSettingForSite` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getauditlogsettingforsite.md
- `getAuditLogsForGlobal` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getauditlogsforglobal.md
- `getAvailableRoles` — Read — https://policylayer.com/tools/migueltvms-tplink-omada-mcp/getavailableroles.md
- …and 296 more: https://policylayer.com/tools/migueltvms-tplink-omada-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=migueltvms-tplink-omada-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/migueltvms-tplink-omada-mcp