Get the top devices by CPU usage for a site, useful for identifying overloaded devices.
AI agents call getDashboardTopCpuUsage 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 and returns CPU usage metrics for devices on a site. It is a read-only operation that retrieves monitoring/observability data without creating, modifying, deleting, or executing commands. The worst-case misuse would be information disclosure about system performance metrics, which has low blast radius.
From the tool's definition Tool name 'getDashboardTopCpuUsage' and description 'Get the top devices by CPU usage for a site' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access getDashboardTopCpuUsage 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 getDashboardTopCpuUsage:
{
"version": "1",
"default": "deny",
"tools": {
"getDashboardTopCpuUsage": {}
}
}getDashboardTopCpuUsage 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 top devices by CPU usage for a site, useful for identifying overloaded devices. 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 getDashboardTopCpuUsage: 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.
getDashboardTopCpuUsage 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 getDashboardTopCpuUsage 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 getDashboardTopCpuUsage. 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.
getDashboardTopCpuUsage 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.