获取 Home Assistant 中所有或指定实体的状态，如灯是否亮着、温度多少、门是否开着
AI agents call ha_get_states 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 queries the current state of smart home devices without modifying, deleting, or executing anything. It retrieves information only (e.g., device status, sensor readings). No side effects, no irreversible actions, no code execution. Low severity because exposing sensor states poses minimal risk compared to other categories.
From the tool's definition The tool description states it '获取...所有或指定实体的状态' (gets/retrieves...the states of all or specified entities), with examples like 'whether lights are on, temperature, whether doors are open'. The tool name 'ha_get_states' uses 'get', a classic read operation.
Attacks that exploit this kind of access
获取 Home Assistant 中所有或指定实体的状态，如灯是否亮着、温度多少、门是否开着. 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 ha_get_states: 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.
ha_get_states 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_get_states 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_get_states. 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_get_states is provided by the Home Assistant MCP Server MCP server (weyand138-netizen/home-assistant-ai-agent-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 →