AI agents call get_clients to retrieve information from UniFi MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of connected clients from the UniFi controller. It queries state without side effects. While the description is empty, the naming convention and context of sibling tools clearly indicate this is a read operation. Even if misused by an agent, it would only expose information about connected devices with minimal security impact.
From the tool's definition Tool name 'get_clients' and sibling tools like 'get_devices', 'get_alarms', 'get_events', 'get_dpi_stats' and 'get_controller_status' all follow read/retrieval patterns. The 'get_' prefix indicates data retrieval with no modification.
Documented attack patterns abuse exactly the kind of access get_clients gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and UniFi MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_clients:
{
"version": "1",
"default": "deny",
"tools": {
"get_clients": {}
}
}get_clients is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_clients. It is categorised as a Read tool in the UniFi MCP MCP Server, which means it retrieves data without modifying state.
Register the UniFi MCP server in PolicyLayer and add a rule for get_clients: 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 UniFi MCP. Nothing to install.
get_clients 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 get_clients 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 get_clients. 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.
get_clients is provided by the UniFi MCP server (jmagar/unifi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from UniFi MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 UniFi MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.