Get all scenes from Fibaro HC3, with optional filtering by room
AI agents call get_scenes 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 queries and retrieves scene data from the smart home system. It performs a read-only operation that returns information about configured scenes, potentially filtered by room. No data is created, modified, deleted, or executed. The information retrieved could inform an attacker about home automation setup, but the direct risk from querying this data alone is low.
From the tool's definition Tool name is 'get_scenes' and description states 'Get all scenes from Fibaro HC3, with optional filtering by room' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all scenes from Fibaro HC3, with optional filtering by room. 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_scenes: 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_scenes 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_scenes 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_scenes. 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_scenes 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 →