getPortSchedulePorts

What getPortSchedulePorts does on Tplink Omada

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

This tool retrieves port schedule information for a site without modifying data, executing commands, or affecting infrastructure. It is a straightforward query operation that gathers configuration information. The low severity reflects that reading port schedule assignments poses minimal risk to system integrity, though the broader server context (arbitrary Omada API calls) represents higher risk at the server level.

From the tool's definition Tool name 'getPort...' with verb 'Get' and description explicitly states 'Get the list of ports' - a retrieval operation with no modification or execution described.

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

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

Questions about getPortSchedulePorts