unifi_locate_device · UniFi Network MCP Server MCP

WHAT IT DOES

What unifi_locate_device does on UniFi Network MCP Server

AI agents invoke unifi_locate_device to trigger actions in UniFi Network MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why unifi_locate_device needs a policy

This tool triggers an external operation on a physical device (flashing its LED), which is an action with real-world effects but minimal blast radius. It doesn't read, write data persistently, delete anything, or involve finances — it executes a device command.

From the tool's definition Enable or disable the locate function (flashing LED) on a device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unifi_locate_device Rate-limited

unifi_locate_device stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "unifi_locate_device": {
      "limits": [
        {
          "counter": "unifi_locate_device_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches UniFi Network MCP Server, so you can run agents against it safely.

FAQ

Questions about unifi_locate_device

What does the unifi_locate_device tool do? +

Enable or disable the locate function (flashing LED) on a device. It is categorised as a Execute tool in the UniFi Network MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on unifi_locate_device? +

Register the UniFi Network MCP Server MCP server in PolicyLayer and add a rule for unifi_locate_device: 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 MCP Server. Nothing to install.

What risk level is unifi_locate_device? +

unifi_locate_device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit unifi_locate_device? +

Yes. Add a rate_limit block to the unifi_locate_device 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 unifi_locate_device completely? +

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

unifi_locate_device is provided by the UniFi Network MCP Server MCP server (ruashots/unifi-network-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.