protect_get_camera
Get detailed camera information by ID.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/protect-get-camera.md
What protect_get_camera does on UniFi Access MCP
AI agents call protect_get_camera to retrieve information from UniFi Access MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why protect_get_camera is rated Low
This tool performs a read-only query operation to retrieve camera information. There are no side effects, data modifications, or irreversible actions. The 'Get' operation and informational retrieval pattern classify it as a Read action with low severity risk.
From the tool's definition Tool name 'protect_get_camera' and description 'Get detailed camera information by ID' indicate retrieval of camera data with no modification capability.
Attacks that exploit this kind of access
The rule that runs protect_get_camera 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_get_camera, this is the rule to start with:
protect_get_camera is read-only, so it stays allowed. 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_get_camera call is checked against it from then on.
Questions about protect_get_camera
Get detailed camera information by ID. It is categorised as a Read tool in the UniFi Access MCP MCP Server, which means it retrieves data without modifying state.
Register the UniFi Access MCP server in PolicyLayer and add a rule for protect_get_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.
protect_get_camera is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the protect_get_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.
Set action: deny in the PolicyLayer policy for protect_get_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.
protect_get_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.
This server
Across the catalogue