Low Risk

get_devices

Get all devices with clean, formatted summaries.

How to control get_devices ↓

What get_devices does on UniFi MCP

AI agents call get_devices 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.

Low Risk

Why get_devices needs a policy

This tool queries and returns device information from the UniFi controller without creating, modifying, or deleting any data. It is purely informational and presents no risk of unintended state changes. While network topology data could theoretically inform reconnaissance, the tool itself is passive and poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'get_devices' and description 'Get all devices with clean, formatted summaries' indicate a retrieval operation with no side effects. The verb 'Get' and absence of modification language confirm read-only intent.

Documented attack patterns abuse exactly the kind of access get_devices gives an agent:

How to control get_devices

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_devices:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_devices": {}
  }
}

get_devices is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register UniFi MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_devices

What does the get_devices tool do? +

Get all devices with clean, formatted summaries. It is categorised as a Read tool in the UniFi MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_devices? +

Register the UniFi MCP server in PolicyLayer and add a rule for get_devices: 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.

What risk level is get_devices? +

get_devices is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_devices? +

Yes. Add a rate_limit block to the get_devices 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.

How do I block get_devices completely? +

Set action: deny in the PolicyLayer policy for get_devices. 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.

What MCP server provides get_devices? +

get_devices 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.

Enforce policy on every UniFi MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.