unifi_force_provision_device
Force re-provision a device, pushing the current configuration from the
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-force-provision-device.md
What unifi_force_provision_device does on UniFi Access MCP
AI agents invoke unifi_force_provision_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_force_provision_device is rated High
Force provisioning pushes configuration to a physical UniFi Access device (e.g., door controller), which is an external operation with real-world effects. It does not simply read or write data in a database — it actively reconfigures hardware. Misuse could disrupt access control systems, lock out users, or cause doors to malfunction. Severity is high due to potential physical security impact.
From the tool's definition 'Force re-provision a device, pushing the current configuration from the' — triggers an active re-provisioning operation on a physical access control device
Attacks that exploit this kind of access
The rule that runs unifi_force_provision_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_force_provision_device, this is the rule to start with:
unifi_force_provision_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_force_provision_device call is checked against it from then on.
Questions about unifi_force_provision_device
Force re-provision a device, pushing the current configuration from the. 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_force_provision_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_force_provision_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_force_provision_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_force_provision_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_force_provision_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