protect_ptz_move
A execute tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/protect-ptz-move.md
What protect_ptz_move does on UniFi Access MCP
AI agents invoke protect_ptz_move 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_ptz_move is rated High
PTZ (Pan-Tilt-Zoom) refers to camera control operations that physically move a camera. This would be an Execute category action as it triggers an external physical operation. However, the description is empty, so confidence is low. The tool appears to belong to UniFi Protect (camera system) rather than UniFi Access, which is unusual for this server context, further reducing confidence.
From the tool's definition Tool name 'protect_ptz_move' suggests controlling PTZ (Pan-Tilt-Zoom) camera movement, which is an external physical operation. Description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs protect_ptz_move 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 protect_ptz_move, this is the rule to start with:
protect_ptz_move 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 protect_ptz_move call is checked against it from then on.
Questions about protect_ptz_move
protect_ptz_move 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 protect_ptz_move: 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.
protect_ptz_move 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 protect_ptz_move 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 protect_ptz_move. 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.
protect_ptz_move 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