unifi-network-mcp

The default `verify_ssl=False` in `UniFiSettings` and its explicit mention as `UNIFI_VERIFY_SSL="false"` in examples is a significant security risk, making connections vulnerable to Man-in-the-Middle (MITM) attacks if not explicitly configured to `True` with proper certificate validation in production environments. Additionally, `aiohttp.CookieJar(unsafe=True)` is used in the `ConnectionManager`, which relaxes cookie security policies and could potentially expose the session to risks under certain conditions (e.g., XSS vulnerabilities in the UniFi web interface). While the project implements granular permissions (`permission_category`, `permission_action`), requires explicit confirmation (`confirm=True`) for destructive actions, and uses robust input validation with JSON schemas, these two critical network security concerns lower the overall score. It is crucial to ensure this server runs in a trusted, isolated environment and that `UNIFI_VERIFY_SSL` is correctly configured for production.