getInternetLoadBalance
Get WAN load balancing configuration for the site gateway. Returns load balancing mode (failover/load balance) and WAN port weights.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getinternetloadbalance.md
What getInternetLoadBalance does on Tplink Omada
AI agents call getInternetLoadBalance 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 getInternetLoadBalance is rated Low
This is a pure read operation that queries network configuration settings. It retrieves existing load balancing parameters without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker gains visibility into WAN configuration but cannot alter network behavior or access without additional write/execute tools.
From the tool's definition Tool name 'getInternetLoadBalance' and description 'Get WAN load balancing configuration' indicate a retrieval operation with no modification of state. The tool returns configuration data (load balancing mode and WAN port weights) without side effects.
Attacks that exploit this kind of access
The rule that runs getInternetLoadBalance 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 getInternetLoadBalance, this is the rule to start with:
getInternetLoadBalance 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 getInternetLoadBalance call is checked against it from then on.
Questions about getInternetLoadBalance
Get WAN load balancing configuration for the site gateway. Returns load balancing mode (failover/load balance) and WAN port weights. 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 getInternetLoadBalance: 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.
getInternetLoadBalance 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 getInternetLoadBalance 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 getInternetLoadBalance. 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.
getInternetLoadBalance 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