Get all known clients (including offline). Shows historical client data from the controller database.
AI agents call unifi-client-history to retrieve information from UniFi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves client history information from the UniFi controller database without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function with no side effects. The blast radius of misuse is minimal—an attacker could enumerate network clients but cannot alter network configuration, execute commands, or cause destructive changes.
From the tool's definition Tool description states 'Get all known clients' and 'Shows historical client data from the controller database.' The verb 'Get' and the passive observation of 'historical data' indicate read-only retrieval with no modification or deletion of data.
Attacks that exploit this kind of access
Get all known clients (including offline). Shows historical client data from the controller database. It is categorised as a Read tool in the UniFi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the UniFi MCP Server MCP server in PolicyLayer and add a rule for unifi-client-history: 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 Server. Nothing to install.
unifi-client-history 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-client-history 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-client-history. 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-client-history is provided by the UniFi MCP Server MCP server (philipvanlewis/unifi-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 →