[DEPRECATED] Use getWanPortsConfig instead. Same GET .../internet/ports-config endpoint. Get detailed WAN port configuration for all gateway WAN ports on the site.
AI agents call getWanPortDetail 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 WAN port configuration data from the TP-Link Omada controller without any side effects. It is a read-only query operation that returns configuration details. The deprecation notice does not change its security classification. Severity is low because exposure of WAN port configuration details alone poses minimal risk unless combined with write/execute capabilities.
From the tool's definition Tool name contains 'get', description states 'Get detailed WAN port configuration' and explicitly references a GET endpoint (GET .../internet/ports-config). No modification, deletion, execution, or financial operations are performed.
Documented attack patterns abuse exactly the kind of access getWanPortDetail 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 getWanPortDetail:
{
"version": "1",
"default": "deny",
"tools": {
"getWanPortDetail": {}
}
}getWanPortDetail 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.
[DEPRECATED] Use getWanPortsConfig instead. Same GET .../internet/ports-config endpoint. Get detailed WAN port configuration for all gateway WAN ports on the site. 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 getWanPortDetail: 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.
getWanPortDetail 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 getWanPortDetail 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 getWanPortDetail. 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.
getWanPortDetail 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.