getDashboardTrafficActivities
Get traffic activity time-series data for a site, showing upload and download trends over time.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getdashboardtrafficactivities.md
What getDashboardTrafficActivities does on Tplink Omada
AI agents call getDashboardTrafficActivities 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 getDashboardTrafficActivities is rated Low
This tool fetches historical network traffic metrics for monitoring/analysis purposes. It has no side effects, does not modify state, does not execute operations, and does not move money. The blast radius of misuse is limited to potential exposure of network traffic patterns, which is a read-level risk.
From the tool's definition Tool name 'getDashboard...' and description states it retrieves 'traffic activity time-series data' and shows 'trends over time' — purely a data query operation with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
The rule that runs getDashboardTrafficActivities 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 getDashboardTrafficActivities, this is the rule to start with:
getDashboardTrafficActivities is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tplink Omada, apply this rule, and every getDashboardTrafficActivities call is checked against it from then on.
Questions about getDashboardTrafficActivities
Get traffic activity time-series data for a site, showing upload and download trends over time. 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 getDashboardTrafficActivities: 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.
getDashboardTrafficActivities 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 getDashboardTrafficActivities 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 getDashboardTrafficActivities. 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.
getDashboardTrafficActivities 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.
More on Tplink Omada, and thousands of servers like it.
This server
Across the catalogue