unifi_upgrade_device
Initiate a firmware upgrade for a device by MAC address (uses cached firmware by default)
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-upgrade-device.md
What unifi_upgrade_device does on UniFi Access MCP
AI agents invoke unifi_upgrade_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 unifi_upgrade_device is rated High
Triggering a firmware upgrade is an external operation that modifies device firmware and causes a reboot/downtime. It is not a simple write (it runs an upgrade process on physical hardware), not destructive in the irreversible-deletion sense, but it executes a significant operational action with potentially wide blast radius if applied to the wrong device or with bad firmware.
From the tool's definition Initiate a firmware upgrade for a device by MAC address
Attacks that exploit this kind of access
The rule that runs unifi_upgrade_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 unifi_upgrade_device, this is the rule to start with:
unifi_upgrade_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 unifi_upgrade_device call is checked against it from then on.
Questions about unifi_upgrade_device
Initiate a firmware upgrade for a device by MAC address (uses cached firmware by default). 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 unifi_upgrade_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.
unifi_upgrade_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 unifi_upgrade_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 unifi_upgrade_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.
unifi_upgrade_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