List configured UniFi controller targets (ids and metadata, no secrets)
AI agents call list_targets to retrieve information from Unifi Network without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about configured targets without modifying state, exposing secrets, executing code, or causing irreversible changes. It is a straightforward query operation with minimal security impact—the worst outcome of misuse would be exposure of non-sensitive target identifiers and metadata.
From the tool's definition Tool name 'list_targets' and description 'List configured UniFi controller targets (ids and metadata, no secrets)' indicate a retrieval operation. The explicit statement 'no secrets' confirms no sensitive data is exposed.
Attacks that exploit this kind of access
List configured UniFi controller targets (ids and metadata, no secrets). It is categorised as a Read tool in the Unifi Network MCP Server, which means it retrieves data without modifying state.
Register the Unifi Network MCP server in PolicyLayer and add a rule for list_targets: 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 Network. Nothing to install.
list_targets 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 list_targets 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 list_targets. 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.
list_targets is provided by the Unifi Network MCP server (unifi-network-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 →