getPortForwardingStatus
Get port forwarding status and rules for a site. Retrieves either User-configured or UPnP-discovered port forwarding rules. Both page and pageSize parameters are required by the API. Call this tool twice (once with type=
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getportforwardingstatus.md
What getPortForwardingStatus does on Tplink Omada
AI agents call getPortForwardingStatus 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 getPortForwardingStatus is rated Low
This tool retrieves port forwarding configuration data from the TP-Link Omada controller without modifying it. While the underlying port forwarding rules could expose network architecture details and represent a potential attack surface if misconfigured, the tool itself performs only data retrieval (Read category).
From the tool's definition Tool name 'getPortForwardingStatus' and description 'Get port forwarding status and rules' indicate data retrieval with no modification. The verb 'get' and 'retrieves' confirm read-only operation.
Attacks that exploit this kind of access
The rule that runs getPortForwardingStatus 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 getPortForwardingStatus, this is the rule to start with:
getPortForwardingStatus 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 getPortForwardingStatus call is checked against it from then on.
Questions about getPortForwardingStatus
Get port forwarding status and rules for a site. Retrieves either User-configured or UPnP-discovered port forwarding rules. Both page and pageSize parameters are required by the API. Call this tool twice (once with type=. 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 getPortForwardingStatus: 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.
getPortForwardingStatus 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 getPortForwardingStatus 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 getPortForwardingStatus. 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.
getPortForwardingStatus 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