Get HC3 Lua Scenes programming documentation including conditions, triggers, actions, and examples
AI agents call get_hc3_lua_scenes_guide 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.
The tool retrieves and queries documentation about Lua scenes programming. It does not modify, execute, delete, or control any smart home devices or system state. Documentation access is a pure read operation with minimal security risk even if accessed inappropriately by an AI agent.
From the tool's definition Tool name contains 'get' and description states 'Get HC3 Lua Scenes programming documentation' — this is a documentation retrieval operation with no side effects on the smart home system.
Attacks that exploit this kind of access
Get HC3 Lua Scenes programming documentation including conditions, triggers, actions, and examples. 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_hc3_lua_scenes_guide: 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_hc3_lua_scenes_guide 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_hc3_lua_scenes_guide 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_hc3_lua_scenes_guide. 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_hc3_lua_scenes_guide 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 →