getLanNetworkList
[DEPRECATED] Use getLanNetworkListV2 instead. This tool returns an aggregated array of all pages from the v2 LAN networks endpoint, whereas getLanNetworkListV2 is explicitly paginated (page/pageSize) and returns a single page payload. Get the list of LAN networks configured in a site, including V...
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getlannetworklist.md
What getLanNetworkList does on Tplink Omada
AI agents call getLanNetworkList 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 getLanNetworkList is rated Low
This tool queries and retrieves network configuration information without creating, modifying, executing, or deleting anything. While network configuration details could theoretically inform an attack, the tool itself performs only a passive read operation with no side effects. Severity is low because it accesses network metadata rather than sensitive secrets or control plane functionality.
From the tool's definition Tool returns 'list of LAN networks' with 'VLAN settings, IP ranges, and DHCP configuration' - pure data retrieval with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs getLanNetworkList 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 getLanNetworkList, this is the rule to start with:
getLanNetworkList 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 getLanNetworkList call is checked against it from then on.
Questions about getLanNetworkList
[DEPRECATED] Use getLanNetworkListV2 instead. This tool returns an aggregated array of all pages from the v2 LAN networks endpoint, whereas getLanNetworkListV2 is explicitly paginated (page/pageSize) and returns a single page payload. Get the list of LAN networks configured in a site, including VLAN settings, IP ranges, and DHCP configuration. 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 getLanNetworkList: 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.
getLanNetworkList 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 getLanNetworkList 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 getLanNetworkList. 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.
getLanNetworkList 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