getGridDashboardOpenVpnTunnelStats
Get OpenVPN tunnel statistics for the site dashboard filtered by role. Returns connection counts, traffic volumes, and status for OpenVPN tunnels. type must be 0 (Server) or 1 (Client).
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getgriddashboardopenvpntunnelstats.md
What getGridDashboardOpenVpnTunnelStats does on Tplink Omada
AI agents call getGridDashboardOpenVpnTunnelStats 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 getGridDashboardOpenVpnTunnelStats is rated Low
This tool queries and retrieves OpenVPN tunnel statistics without modifying, deleting, or executing operations. It is a read-only information retrieval operation. The low severity reflects that OpenVPN tunnel statistics are operational/diagnostic data with no direct impact on system control or data integrity.
From the tool's definition Tool name contains 'get' and description states it 'Returns connection counts, traffic volumes, and status' with no mention of modifications, deletions, or state changes. The function retrieves dashboard statistics for OpenVPN tunnels.
Attacks that exploit this kind of access
The rule that runs getGridDashboardOpenVpnTunnelStats 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 getGridDashboardOpenVpnTunnelStats, this is the rule to start with:
getGridDashboardOpenVpnTunnelStats 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 getGridDashboardOpenVpnTunnelStats call is checked against it from then on.
Questions about getGridDashboardOpenVpnTunnelStats
Get OpenVPN tunnel statistics for the site dashboard filtered by role. Returns connection counts, traffic volumes, and status for OpenVPN tunnels. type must be 0 (Server) or 1 (Client). 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 getGridDashboardOpenVpnTunnelStats: 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.
getGridDashboardOpenVpnTunnelStats 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 getGridDashboardOpenVpnTunnelStats 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 getGridDashboardOpenVpnTunnelStats. 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.
getGridDashboardOpenVpnTunnelStats 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