device_action · Unifi MCP: Risk & Policy

WHAT IT DOES

What device_action does on Unifi

AI agents invoke device_action to trigger actions in Unifi. 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 device_action needs a policy

This tool executes commands that trigger real-world effects (device reboot) on network hardware. While not destructive in the sense of data loss, restarting devices disrupts network availability and services. This is an Execute rather than Write because it invokes an operation with side effects beyond data modification.

From the tool's definition Tool description states it 'Execute[s] an action on an adopted device' with support for 'RESTART (reboot)'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

device_action Rate-limited

device_action 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": {
    "device_action": {
      "limits": [
        {
          "counter": "device_action_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, so you can run agents against it safely.

FAQ

Questions about device_action

What does the device_action tool do? +

Execute an action on an adopted device. Currently supports RESTART (reboot). It is categorised as a Execute tool in the Unifi MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on device_action? +

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

What risk level is device_action? +

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

Can I rate-limit device_action? +

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

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

device_action is provided by the Unifi MCP server (pproenca/unifi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.