UniFi Internal API MCP Server

list_rogue_aps

Discover rogue access points seen by your managed APs, filtering by time window to identify neighboring Wi-Fi networks not under your control.

Instructions

List rogue (neighboring) access points detected by managed APs.

Returns APs seen by your network that are not part of your UniFi deployment, within the specified time window.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_rogue_aps"
  }
}

Input Schema

Name	Required	Description	Default
`within`	No	Hours to look back for rogue AP detections

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden for behavioral disclosure. It adds context (detected by managed APs, time window) but does not explicitly state read-only nature, authentication needs, or pagination behavior. As a list tool, the non-destructive nature is implied but not explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the primary action, and every word earns its place. It is concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one optional parameter), full schema coverage, and presence of an output schema, the description is complete. It provides enough context for the agent to understand the tool's scope and behavior without missing critical information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the parameter 'within' is already well-described in the schema. The description only reinforces the time-window concept without adding new semantic detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: 'List rogue (neighboring) access points detected by managed APs.' It distinguishes from siblings like list_known_rogue_aps by specifying 'not part of your UniFi deployment.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies its use case (identifying neighboring APs not in the deployment) and the time-window parameter. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of full explicit guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server