camera_proxy_get
AI agents call camera_proxy_get to retrieve information from Homeassistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' suffix and proxy pattern strongly indicate this tool retrieves or streams camera video/image data without modifying state. While Read-category tools typically carry low severity, camera feeds can expose sensitive home security information (occupancy, layout, activity patterns), elevating this to medium severity.
From the tool's definition Tool name 'camera_proxy_get' indicates a retrieval operation (GET pattern) for camera feed data. The tool is grouped among Home Assistant control tools that include camera_control, suggesting it accesses camera-related information.
Attacks that exploit this kind of access
camera_proxy_get. It is categorised as a Read tool in the Homeassistant MCP Server, which means it retrieves data without modifying state.
Register the Homeassistant MCP server in PolicyLayer and add a rule for camera_proxy_get: 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 Homeassistant. Nothing to install.
camera_proxy_get 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 camera_proxy_get 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 camera_proxy_get. 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.
camera_proxy_get is provided by the Homeassistant MCP server (robbrad/homeassistant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →