protect_reboot_camera

A execute tool on the UniFi Access MCP server.

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/protect-reboot-camera.md

What protect_reboot_camera does on UniFi Access MCP

AI agents invoke protect_reboot_camera 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 protect_reboot_camera is rated High

Rebooting a camera is an external operation that disrupts surveillance/recording and cannot be easily undone during the reboot window. The description is empty, so confidence is reduced, but the name strongly implies a disruptive execute action. It doesn't destroy data but causes operational disruption to a physical device.

From the tool's definition Tool name 'protect_reboot_camera' implies rebooting a camera device, which is an irreversible trigger of an external hardware operation.

Questions about protect_reboot_camera

What does the protect_reboot_camera tool do? +

protect_reboot_camera 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.

How do I enforce a policy on protect_reboot_camera? +

Register the UniFi Access MCP server in PolicyLayer and add a rule for protect_reboot_camera: 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 protect_reboot_camera? +

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

Can I rate-limit protect_reboot_camera? +

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

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

protect_reboot_camera 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.