Get a list of all automations from Home Assistant This function retrieves all automations configured in Home Assistant, including their IDs, entity IDs, state, and display names. Returns: A list of automation dictionaries, each containing id, entity_id, state, and alias (friendly name) fields. Ex...
AI agents call list_automations 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 and returns automation configuration data without side effects. It is a read-only operation that retrieves state information. While the broader server includes Execute and Destructive tools (call_service_tool, entity_action), this specific tool only lists automations without triggering or modifying them.
From the tool's definition Tool description states it 'retrieves all automations configured in Home Assistant' and 'Returns: A list of automation dictionaries'. The function performs data retrieval with no modification, deletion, or execution of automations.
Documented attack patterns abuse exactly the kind of access list_automations 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_automations:
{
"version": "1",
"default": "deny",
"tools": {
"list_automations": {}
}
}list_automations 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 a list of all automations from Home Assistant This function retrieves all automations configured in Home Assistant, including their IDs, entity IDs, state, and display names. Returns: A list of automation dictionaries, each containing id, entity_id, state, and alias (friendly name) fields. Examples: Returns all automation objects with state and friendly names. 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_automations: 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_automations 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_automations 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_automations. 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_automations 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.