getIspLoad

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/getispload.md

WHAT IT DOES

What getIspLoad does on Tplink Omada

AI agents call getIspLoad 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 getIspLoad is rated Low

This tool retrieves historical or current network performance metrics from the TP-Link Omada controller. It performs no state changes, does not execute commands, delete data, or trigger external actions. It is a straightforward read operation on monitoring/analytics data, comparable to querying dashboard statistics.

From the tool's definition Tool description explicitly states 'Get per-WAN ISP link load' and 'Shows traffic volume and utilization' — retrieve operations with no modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

getIspLoad Allowed

getIspLoad 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": {
    "getIspLoad": {}
  }
}

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 getIspLoad call is checked against it from then on.

FAQ

Questions about getIspLoad

What does the getIspLoad tool do? +

Get per-WAN ISP link load over a time range. Shows traffic volume and utilization per internet uplink. Useful for understanding load balancing behaviour, identifying saturated WAN links, and analysing failover events. start and end are Unix timestamps in seconds. 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 getIspLoad? +

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

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

Can I rate-limit getIspLoad? +

Yes. Add a rate_limit block to the getIspLoad 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 getIspLoad completely? +

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

getIspLoad 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 →