AI agents call get_entity 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.
This tool queries smart home entity data (device states, properties) without side effects. Home Assistant entities are typically passive data representing device status. No creation, modification, deletion, code execution, or financial impact occurs. The primary risk is information disclosure about home automation setup, which is low severity.
From the tool's definition Tool name 'get_entity' indicates a retrieval operation. Contextually, on a Home Assistant MCP server alongside tools like 'get_entities_by_area', 'get_history', and 'get_statistics', this tool clearly retrieves entity state data without modifying anything.
Documented attack patterns abuse exactly the kind of access get_entity 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 get_entity:
{
"version": "1",
"default": "deny",
"tools": {
"get_entity": {}
}
}get_entity 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.
get_entity. 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 get_entity: 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.
get_entity 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_entity 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_entity. 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_entity 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.