getUpnpSetting
Get UPnP (Universal Plug and Play) setting for the site. Shows whether UPnP port mapping is enabled on the gateway.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getupnpsetting.md
What getUpnpSetting does on Tplink Omada
AI agents call getUpnpSetting 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 getUpnpSetting is rated Low
This tool retrieves the current UPnP configuration status without modifying it, executing code, or causing destructive side effects. It is a passive query of gateway settings, fitting the Read category.
From the tool's definition Tool name 'getUpnpSetting' and description 'Get UPnP...setting...Shows whether UPnP port mapping is enabled' indicate a read-only retrieval of configuration state with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs getUpnpSetting 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 getUpnpSetting, this is the rule to start with:
getUpnpSetting 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 getUpnpSetting call is checked against it from then on.
Questions about getUpnpSetting
Get UPnP (Universal Plug and Play) setting for the site. Shows whether UPnP port mapping is enabled on the gateway. 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 getUpnpSetting: 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.
getUpnpSetting 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 getUpnpSetting 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 getUpnpSetting. 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.
getUpnpSetting 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