Get all connected clients/devices on the UniFi network
AI agents call unifi_get_clients to retrieve information from Multi-Tool MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about connected network devices from a UniFi controller. While it is fundamentally a Read operation (no side effects, only querying state), the severity is elevated to medium because: (1) the data retrieved could include sensitive network topology and device information useful for reconnaissance; (2) UniFi controllers manage network infrastructure; (3) an AI agent with this capability…
From the tool's definition Tool name 'unifi_get_clients' and description 'Get all connected clients/devices on the UniFi network' indicate a query/retrieval operation with no data modification.
Attacks that exploit this kind of access
Get all connected clients/devices on the UniFi network. It is categorised as a Read tool in the Multi-Tool MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi-Tool MCP Server MCP server in PolicyLayer and add a rule for unifi_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 Multi-Tool MCP Server. Nothing to install.
unifi_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 unifi_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 unifi_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.
unifi_get_clients is provided by the Multi-Tool MCP Server MCP server (shawn-falconbury/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →