AI agents call list_entities to retrieve information from Hass-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
'list_entities' appears to be a query/retrieval tool that returns a list of Home Assistant entities, consistent with the Read category. The absence of description reduces confidence slightly, but the function name and context of sibling read-only tools strongly suggest no side effects or state modifications occur.
From the tool's definition Tool name 'list_entities' combined with sibling tools that include read-only operations like 'get_entities_by_area', 'get_entity', 'get_history', and 'get_statistics' indicates this retrieves/queries entity data.
Documented attack patterns abuse exactly the kind of access list_entities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hass-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_entities:
{
"version": "1",
"default": "deny",
"tools": {
"list_entities": {}
}
}list_entities is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_entities. It is categorised as a Read tool in the Hass-MCP MCP Server, which means it retrieves data without modifying state.
Register the Hass- 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 Hass-MCP. 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 Hass- MCP server (voska/hass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Hass-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Hass-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.