New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

getPortalPort

Get the portal port configuration for the controller web interface.

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/getportalport.md

What getPortalPort does on Tplink Omada

AI agents call getPortalPort 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 getPortalPort is rated Low

This tool retrieves portal port configuration settings from the TP-Link Omada controller. It performs no modifications, does not execute commands, and has no destructive or financial implications. The 'get' prefix confirms it is a simple data retrieval operation. Low severity because knowing the portal port is generally non-sensitive network configuration information that is often publicly discoverable.

From the tool's definition Tool name 'getPortalPort' and description 'Get the portal port configuration for the controller web interface' indicate a read-only retrieval operation that queries existing configuration without modifying or executing anything.

Questions about getPortalPort

What does the getPortalPort tool do? +

Get the portal port configuration for the controller web interface. 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 getPortalPort? +

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

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

Can I rate-limit getPortalPort? +

Yes. Add a rate_limit block to the getPortalPort 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 getPortalPort completely? +

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tplink Omada's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.