List all entities, optionally filtered by domain (light, sensor, etc.)
AI agents call list_entities to retrieve information from Home Assistant MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns a list of smart home entities (devices/sensors). It has no side effects, does not execute commands, does not modify state, and does not delete data. It is a straightforward data retrieval operation with minimal security risk—the worst case exposure is information disclosure about what devices exist in the home automation system.
From the tool's definition Tool name 'list_entities' and description 'List all entities, optionally filtered by domain' indicate a query operation that retrieves data without modification. The verb 'list' is explicitly a retrieval action.
Attacks that exploit this kind of access
List all entities, optionally filtered by domain (light, sensor, etc.). It is categorised as a Read tool in the Home Assistant MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Home Assistant MCP Server MCP server in PolicyLayer and add a rule for list_entities: 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 Home Assistant MCP Server. Nothing to install.
list_entities 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 list_entities 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 list_entities. 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.
list_entities is provided by the Home Assistant MCP Server MCP server (mjrestivo16/mcp-homeassistant). 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 →