access_reboot_device
A execute tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/access-reboot-device.md
What access_reboot_device does on UniFi Access MCP
AI agents invoke access_reboot_device to trigger actions in UniFi Access MCP. 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 access_reboot_device is rated High
Rebooting a device is an external operation that causes a physical device to restart, disrupting access control operations. This is an Execute-level action (triggering an external hardware operation) with high severity since rebooting an access control device (e.g., a door controller) could disrupt physical security systems, temporarily unlock/lock doors, or deny access to personnel.
From the tool's definition Tool name 'access_reboot_device' implies triggering a reboot operation on a physical UniFi Access device. Description is empty, so classification is based on name alone.
Attacks that exploit this kind of access
The rule that runs access_reboot_device safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UniFi Access MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For access_reboot_device, this is the rule to start with:
access_reboot_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.
The button opens the PolicyLayer dashboard: create your workspace, connect UniFi Access MCP, apply this rule, and every access_reboot_device call is checked against it from then on.
Questions about access_reboot_device
access_reboot_device is a execute tool on the UniFi Access MCP server. It is categorised as a Execute tool in the UniFi Access MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the UniFi Access MCP server in PolicyLayer and add a rule for access_reboot_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 Access MCP. Nothing to install.
access_reboot_device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the access_reboot_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.
Set action: deny in the PolicyLayer policy for access_reboot_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.
access_reboot_device is provided by the UniFi Access MCP server (pypi:unifi-protect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UniFi Access, and thousands of servers like it.
Across the catalogue