getCableTestFullResults
Get full cable test results for all ports on a switch. Returns detailed per-port diagnostic data including cable status (OK/open/short), estimated cable length, and fault location. More detailed than getCableTestLogs.
This record as markdown: /tools/migueltvms-tplink-omada-mcp/getcabletestfullresults.md
What getCableTestFullResults does on Tplink Omada
AI agents call getCableTestFullResults 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 getCableTestFullResults is rated Low
This tool retrieves cable test diagnostic information from network switch ports. It performs a read-only query of existing test results and status data (cable status, length, fault location). There is no creation, modification, deletion, or execution of commands. The data returned is diagnostic telemetry with no capability to change device configuration or state.
From the tool's definition Tool name 'getCableTestFullResults' and description 'Get full cable test results' — retrieves diagnostic data with no modification or side effects. Returns 'detailed per-port diagnostic data' without altering system state.
Attacks that exploit this kind of access
The rule that runs getCableTestFullResults 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 getCableTestFullResults, this is the rule to start with:
getCableTestFullResults 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 getCableTestFullResults call is checked against it from then on.
Questions about getCableTestFullResults
Get full cable test results for all ports on a switch. Returns detailed per-port diagnostic data including cable status (OK/open/short), estimated cable length, and fault location. More detailed than getCableTestLogs. 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 getCableTestFullResults: 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.
getCableTestFullResults 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 getCableTestFullResults 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 getCableTestFullResults. 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.
getCableTestFullResults 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