DFS Reset

Detect DFS radar events and reset Ubiquiti airOS devices to restore configured frequencies, managed by UISP NMS. Use when checking whether WISP APs were forc...

Security Scan

The skill's instructions, listed tools, and described workflow match its stated purpose (detect DFS shifts and reset Ubiquiti airOS devices via a UISP/MCP control plane); there are no obvious mismatches or hidden installs, but the SKILL.md omits explicit auth/credential declarations and relies on an external MCP endpoint which you should verify before use.

Purpose & Capability

Name, description, and the provided tool list (list_devices, detect_dfs, reset_device, get_clients, etc.) are coherent with the stated goal of detecting DFS events and rebooting UISP-managed airOS APs. The SKILL.md references an MCP control plane and an example repo which aligns with the skill's purpose.

Instruction Scope

Runtime instructions confine actions to device listing, DFS detection, stats/clients collection, and operator-confirmed resets. There are no instructions to read arbitrary local files or to exfiltrate data to third‑party endpoints; safety rules explicitly require operator confirmation before resets.

Install Mechanism

This is an instruction-only skill with no install spec and no bundled code; nothing is written to disk by the skill itself based on the provided metadata, which is the lowest-risk install profile.

Credentials

The SKILL.md expects use of an MCP endpoint/session but declares no required environment variables or credentials. In practice the toolset will need authenticated access to the UISP/MCP control plane and to the managed devices; the lack of explicit credential requirements is an omission the operator should confirm (how auth is provided, what secrets are used, and whether least privilege is enforced).

Persistence & Privilege

always is false and the skill does not request permanent presence or attempt to modify other skills or system-wide settings. Autonomous invocation is allowed (default) but not combined with other red flags here.

Assessment

This skill appears to do what it says, but verify the following before installing: (1) Confirm how the MCP/UISP authentication is provided (API key, session token, service account) and ensure least privilege access for management actions. (2) Audit and review the actual MCP server implementation (the linked repo or your deployment) to ensure it does not contain hidden endpoints or data exfil logic. (3) Restrict network access so the skill only reaches the expected UISP/MCP endpoints and internal AP IP ranges. (4) Test in a lab or on a non-production site first; ensure operator confirmation prompts work as documented so resets cannot occur without explicit approval. (5) Ensure logging and change-audit are enabled on your NMS to track any resets or actions initiated by the agent.

Use the MCP endpoint configured for this deployment. Placeholder example:

https://example.invalid:8443

Source project for this MCP server:

https://github.com/wispnet/wisp-reset-airos-mcp/

This MCP server uses streamable HTTP with session-based MCP initialization.

Expected workflow

1. Initialize an MCP session.
2. Send notifications/initialized.
3. Call tools on the same session.

Core workflow

1. Detect: use detect_dfs on an AP to compare configured vs actual frequency.
2. Report: tell the operator which APs shifted and what channels they moved to.
3. Reset: use reset_device only after operator confirmation.
4. Verify: re-run detect_dfs after about 60 seconds.

Tool reference

list_devices(site=None)

List UISP-managed devices, optionally filtered by site.

get_device(identifier)

Get detailed device information by name, IP, or UISP device ID.

detect_dfs(ip)

Compare UISP configured frequency with the device's actual operating frequency.

reset_device(identifier)

Reboot a device through UISP. Always confirm with the operator first.

get_clients(ip)

Fetch connected stations for an AP.

get_device_stats(ip)

Fetch AP health details including uptime, CPU, memory, and temperature.

sweep_clients(site=None)

Collect client tables across APs concurrently.

Safety rules

1. Never call reset_device without explicit operator confirmation.
2. Do not mix broad sweep actions with reset actions in one step.
3. Treat DFS shifts as informational until the operator wants corrective action.
4. Verify every reset with a follow-up detect_dfs.
5. Expect partial sweep results when some APs are unreachable.

Signal interpretation

• Better than -65 dBm: good
• -65 to -75 dBm: fair
• -75 to -80 dBm: poor
• Worse than -80 dBm: unusable

Typical clean noise floor is around -90 to -95 dBm. Noise above -85 dBm suggests interference.