Récupère la liste de tous les services disponibles dans Home Assistant
AI agents call get_services 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 and returns metadata about available services without modifying, executing, or deleting any data or state. It is purely informational and carries minimal risk—at worst, an attacker learns what capabilities are available, which is reconnaissance-level exposure.
From the tool's definition Tool name is 'get_services' and description states 'Récupère la liste de tous les services disponibles dans Home Assistant' (Retrieves the list of all available services in Home Assistant). This is a pure retrieval operation with no side effects.
Attacks that exploit this kind of access
Récupère la liste de tous les services disponibles dans 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 get_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 Home Assistant MCP Server. Nothing to install.
get_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 get_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 get_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.
get_services is provided by the Home Assistant MCP Server MCP server (jonathan97480/mcphomeassistant). 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 →