AI agents call ha_states to retrieve information from Yaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | HA URL (default: http://homeassistant.local:8123) |
token | string | — | HA long-lived access token |
filter | string | — | Filter entities (e.g. 'light', 'vacuum', 'switch', 'climate', 'sensor') |
Parameters from the server's own tool schema.
Even though ha_states only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (token)
Attacks that exploit this kind of access
Get Home Assistant entity states. Control Xiaomi, Philips Hue, or any HA-connected device. Filter by entity type (light, switch, vacuum, climate, sensor, etc.). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
ha_states accepts 3 parameters: url, token, filter. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for ha_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 Yaver. Nothing to install.
ha_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_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_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_states is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.