Get list of available IP camera types for plugin installation.
AI agents call get_ip_cameras to retrieve information from HC3 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information (a list of available IP camera types) from the Fibaro HC3 system. It has no side effects, does not execute operations, create/modify/delete data, or move resources. It is a pure read operation that returns static or semi-static enumeration data useful for the UI or decision-making, making it a Read category tool with low severity.
From the tool's definition Tool name 'get_ip_cameras' and description 'Get list of available IP camera types for plugin installation' indicate a query operation that retrieves a list of available camera types without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get list of available IP camera types for plugin installation. It is categorised as a Read tool in the HC3 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HC3 MCP Server MCP server in PolicyLayer and add a rule for get_ip_cameras: 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 HC3 MCP Server. Nothing to install.
get_ip_cameras 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 get_ip_cameras 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 get_ip_cameras. 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.
get_ip_cameras is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_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 →