AI agents call unifi_get_network_summary to retrieve information from Homelab 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 network statistics and configuration overview from Unifi without making changes. It falls squarely into the Read category as it performs passive information retrieval. The severity is low because exposing network summary information to an AI agent poses minimal risk—it discloses no sensitive credentials, enables no configuration changes, and affects no network operations.
From the tool's definition Tool description explicitly states 'Get network overview' and 'Fast summary view', indicating retrieval of existing network information (VLANs, device count, client count) without modification or destructive capability.
Attacks that exploit this kind of access
Get network overview: VLANs, device count, client count. Fast summary view. It is categorised as a Read tool in the Homelab MCP Server, which means it retrieves data without modifying state.
Register the Homelab MCP server in PolicyLayer and add a rule for unifi_get_network_summary: 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 Homelab. Nothing to install.
unifi_get_network_summary 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_network_summary 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_network_summary. 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_network_summary is provided by the Homelab MCP server (myraffy/homelab-mcp). 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 →