Get VPN tunnel statistics filtered by role. Returns connection counts, traffic volumes, and status for VPN tunnels. type must be 0 (Server) or 1 (Client). Use getVpnTunnelStats for a broader summary.
AI agents call getGridDashboardTunnelStats 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 retrieves and queries VPN tunnel statistics filtered by role. It performs no side effects, does not modify any state, does not execute code or commands, and does not move data or delete anything. It is a straightforward read operation on monitoring/telemetry data. The low severity reflects that misuse would only expose information already available to authenticated users with appropriate role access.
From the tool's definition Tool description states 'Get VPN tunnel statistics' and 'Returns connection counts, traffic volumes, and status' - purely retrieval operations with no modification, deletion, or execution of commands.
Documented attack patterns abuse exactly the kind of access getGridDashboardTunnelStats 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 getGridDashboardTunnelStats:
{
"version": "1",
"default": "deny",
"tools": {
"getGridDashboardTunnelStats": {}
}
}getGridDashboardTunnelStats 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 VPN tunnel statistics filtered by role. Returns connection counts, traffic volumes, and status for VPN tunnels. type must be 0 (Server) or 1 (Client). Use getVpnTunnelStats for a broader summary. 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 getGridDashboardTunnelStats: 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.
getGridDashboardTunnelStats 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 getGridDashboardTunnelStats 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 getGridDashboardTunnelStats. 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.
getGridDashboardTunnelStats 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.