unifi_restart_device · Multi-Tool MCP Server MCP

WHAT IT DOES

What unifi_restart_device does on Multi-Tool MCP Server

AI agents invoke unifi_restart_device to trigger actions in Multi-Tool 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_restart_device needs a policy

Restarting network devices is an Execute-class action because it runs an external operation that causes immediate, observable effects in network infrastructure (temporary outage of that device). It is not Destructive because the restart is reversible and does not permanently delete or corrupt data.

From the tool's definition Tool name and description: 'unifi_restart_device' with purpose to 'Restart a UniFi device (access point, switch, etc.)'. This triggers an external operation on network infrastructure whose effects depend on which device is targeted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unifi_restart_device Rate-limited

unifi_restart_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_restart_device": {
      "limits": [
        {
          "counter": "unifi_restart_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 Multi-Tool MCP Server, so you can run agents against it safely.

FAQ

Questions about unifi_restart_device

What does the unifi_restart_device tool do? +

Restart a UniFi device (access point, switch, etc.). It is categorised as a Execute tool in the Multi-Tool 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_restart_device? +

Register the Multi-Tool MCP Server MCP server in PolicyLayer and add a rule for unifi_restart_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 Multi-Tool MCP Server. Nothing to install.

What risk level is unifi_restart_device? +

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

Can I rate-limit unifi_restart_device? +

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

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

unifi_restart_device is provided by the Multi-Tool MCP Server MCP server (shawn-falconbury/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.