unifi_force_provision_device

Force re-provision a device, pushing the current configuration from the

SERVERUniFi Access MCP SOURCEpypi:unifi-protect-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about unifi_force_provision_device

What does the unifi_force_provision_device tool do? +

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.

How do I enforce a policy on unifi_force_provision_device? +

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.

What risk level is unifi_force_provision_device? +

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

Can I rate-limit unifi_force_provision_device? +

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.

How do I block unifi_force_provision_device completely? +

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.

What MCP server provides unifi_force_provision_device? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of UniFi Access's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.