[DEPRECATED] Use getPortForwardingList instead. Same GET .../nat/port-forwardings endpoint. getPortForwardingList exposes explicit pagination params. List all NAT port forwarding rules for a site: external port, internal IP:port, protocol, enabled state, and rule name. Use getPortForwardingStatus...
AI agents call listPortForwardingRules 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 is a read-only operation that retrieves and lists configuration data (NAT port forwarding rules). However, the information disclosed (internal IP addresses, enabled port forwarding rules, protocol details) could be sensitive for network reconnaissance or attack planning, warranting medium severity. The tool performs no side effects and cannot execute code or modify network rules.
From the tool's definition Tool description explicitly states 'List all NAT port forwarding rules' with details on external port, internal IP:port, protocol, enabled state, and rule name. Uses GET endpoint (.../nat/port-forwardings). No modification, deletion, or execution indicated.
Documented attack patterns abuse exactly the kind of access listPortForwardingRules 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 listPortForwardingRules:
{
"version": "1",
"default": "deny",
"tools": {
"listPortForwardingRules": {}
}
}listPortForwardingRules 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 getPortForwardingList instead. Same GET .../nat/port-forwardings endpoint. getPortForwardingList exposes explicit pagination params. List all NAT port forwarding rules for a site: external port, internal IP:port, protocol, enabled state, and rule name. Use getPortForwardingStatus to check User vs UPnP rule state. 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 listPortForwardingRules: 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.
listPortForwardingRules 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 listPortForwardingRules 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 listPortForwardingRules. 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.
listPortForwardingRules 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.