Get Home Assistant error log
AI agents call error_log 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 retrieves historical error log data from Home Assistant for diagnostic or monitoring purposes. There is no indication it modifies, deletes, executes code, or creates financial obligations. Reading logs is a safe, non-destructive operation. The low severity reflects that error logs typically contain non-sensitive operational information, and misuse poses minimal risk to the smart home system itself.
From the tool's definition Tool is named 'error_log' and described as 'Get Home Assistant error log' — the word 'Get' and the action of retrieving log data indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Get Home Assistant error log. 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 error_log: 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.
error_log 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 error_log 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 error_log. 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.
error_log is provided by the Home Assistant MCP Server MCP server (oleander/home-assistant-mcp-server). 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 →