getGatewayPorts

SERVERTplink Omada SOURCEmigueltvms/tplink-omada-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/migueltvms-tplink-omada-mcp/getgatewayports.md

WHAT IT DOES

What getGatewayPorts does on Tplink Omada

AI agents call getGatewayPorts 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.

RISK

Why getGatewayPorts is rated Low

This tool queries network device information and returns status/metrics data without any side effects. It is a straightforward data retrieval operation analogous to network monitoring or inventory queries. The blast radius from misuse is minimal—an attacker gains visibility into network port configuration and statistics but cannot modify infrastructure, execute commands, or cause harm through this tool alone.

From the tool's definition Tool retrieves gateway port details including 'link status, speed, IP address, bytes in/out, and port profile' with no modification, deletion, or execution capability described.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getGatewayPorts 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 getGatewayPorts, this is the rule to start with:

getGatewayPorts Allowed

getGatewayPorts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getGatewayPorts": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tplink Omada, apply this rule, and every getGatewayPorts call is checked against it from then on.

FAQ

Questions about getGatewayPorts

What does the getGatewayPorts tool do? +

Get all WAN and LAN port details for a specific gateway: link status, speed, IP address, bytes in/out, and port profile. More detailed than getGatewayWanStatus or getGatewayLanStatus. Use listDevices to get the gatewayMac. It is categorised as a Read tool in the Tplink Omada MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getGatewayPorts? +

Register the Tplink Omada MCP server in PolicyLayer and add a rule for getGatewayPorts: 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.

What risk level is getGatewayPorts? +

getGatewayPorts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getGatewayPorts? +

Yes. Add a rate_limit block to the getGatewayPorts 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.

How do I block getGatewayPorts completely? +

Set action: deny in the PolicyLayer policy for getGatewayPorts. 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.

What MCP server provides getGatewayPorts? +

getGatewayPorts 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.

KEEP EXPLORING

More on Tplink Omada, and thousands of servers like it.

This server

All 327 Tplink Omada tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →