AI agents call ha_list_entity_registry to retrieve information from Hass without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about Home Assistant entity registry entries. It performs no state modifications, deletions, or control actions. It is purely informational and safe to call. The blast radius of misuse is minimal—an agent could only learn about available entities in the Home Assistant system, which is read-only access to metadata.
From the tool's definition Tool name contains 'list' and description states 'List Home Assistant entity registry entries' — a straightforward data retrieval operation with no side effects.
Attacks that exploit this kind of access
List Home Assistant entity registry entries. It is categorised as a Read tool in the Hass MCP Server, which means it retrieves data without modifying state.
Register the Hass MCP server in PolicyLayer and add a rule for ha_list_entity_registry: 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 Hass. Nothing to install.
ha_list_entity_registry 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 ha_list_entity_registry 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 ha_list_entity_registry. 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.
ha_list_entity_registry is provided by the Hass MCP server (thewhykiki/hass-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 →