getTrafficStats

SERVERTplink Omada SOURCEmigueltvms/tplink-omada-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/migueltvms-tplink-omada-mcp/gettrafficstats.md

WHAT IT DOES

What getTrafficStats does on Tplink Omada

AI agents call getTrafficStats 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.

RISK

Why getTrafficStats is rated Low

This tool queries and retrieves network traffic statistics from the Omada dashboard. It performs a read-only GET operation with no side effects—it neither modifies data, executes commands, nor deletes anything. The deprecation note confirms it accesses the same GET endpoint as its successor, reinforcing its read-only nature.

From the tool's definition Tool name 'getTrafficStats' and description state it retrieves 'traffic activity statistics' and 'throughput data' via a GET endpoint, with no mention of modification, deletion, or execution of commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

getTrafficStats Allowed

getTrafficStats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tplink Omada, apply this rule, and every getTrafficStats call is checked against it from then on.

FAQ

Questions about getTrafficStats

What does the getTrafficStats tool do? +

[DEPRECATED] Use getDashboardTrafficActivities instead. Same GET .../dashboard/traffic-activities endpoint. Get traffic activity statistics for a site, including upload/download throughput data from the dashboard traffic activities endpoint. It is categorised as a Read tool in the Tplink Omada MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getTrafficStats? +

Register the Tplink Omada MCP server in PolicyLayer and add a rule for getTrafficStats: 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.

What risk level is getTrafficStats? +

getTrafficStats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getTrafficStats? +

Yes. Add a rate_limit block to the getTrafficStats 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.

How do I block getTrafficStats completely? +

Set action: deny in the PolicyLayer policy for getTrafficStats. 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.

What MCP server provides getTrafficStats? +

getTrafficStats 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.

KEEP EXPLORING

More on Tplink Omada, and thousands of servers like it.

This server

All 327 Tplink Omada tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →