analyze_home
Home-wide analysis. action: health (offline + battery), safety_audit, energy, stale_items, orphans (broken links),
This record as markdown: /tools/deswong-openhab-mcp/analyze-home.md
What analyze_home does on Openhab
AI agents call analyze_home to retrieve information from Openhab without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why analyze_home is rated Low
Although 'analyze_home' accesses potentially sensitive operational data (device health, safety audit results, energy consumption), it does not create, modify, delete, execute commands, or move money. It is fundamentally a diagnostic/read operation.
From the tool's definition The tool performs analysis and diagnostic operations: 'health (offline + battery)', 'safety_audit', 'energy', 'stale_items', 'orphans (broken links)'.
Attacks that exploit this kind of access
The rule that runs analyze_home safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Openhab, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For analyze_home, this is the rule to start with:
analyze_home 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 Openhab, apply this rule, and every analyze_home call is checked against it from then on.
Questions about analyze_home
Home-wide analysis. action: health (offline + battery), safety_audit, energy, stale_items, orphans (broken links),. It is categorised as a Read tool in the Openhab MCP Server, which means it retrieves data without modifying state.
Register the Openhab MCP server in PolicyLayer and add a rule for analyze_home: 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 Openhab. Nothing to install.
analyze_home 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 analyze_home 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 analyze_home. 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.
analyze_home is provided by the Openhab MCP server (deswong/openhab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Openhab, and thousands of servers like it.
This server
Across the catalogue