AI agents call ha_list_services to retrieve information from Hass without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available Home Assistant services without modifying, executing, or deleting any data. It is purely informational—listing service definitions and their parameters. There is no blast radius from an AI agent calling this tool, as it cannot cause state changes or trigger actions on its own.
From the tool's definition Tool name 'ha_list_services' and description 'List Home Assistant services and their fields' indicate a query/retrieval operation with no side effects. The verb 'List' is explicitly a Read operation per the classification rules.
Attacks that exploit this kind of access
List Home Assistant services and their fields. It is categorised as a Read tool in the Hass MCP Server, which means it retrieves data without modifying state.
Register the Hass MCP server in PolicyLayer and add a rule for ha_list_services: 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. Nothing to install.
ha_list_services 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_list_services 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_list_services. 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_list_services is provided by the Hass MCP server (thewhykiki/hass-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 →