logbook_query
AI agents call logbook_query to retrieve information from Homeassistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Logbooks are read-only historical records. The tool name strongly suggests retrieval ('query') rather than modification, creation, or execution. Even without a description, logbook tools universally fetch past events/data. Severity is low because logbook data is typically non-sensitive operational history with minimal blast radius if misused.
From the tool's definition Tool named 'logbook_query' with no description; 'query' implies data retrieval. In Home Assistant context, logbook access retrieves historical event logs without modifying state.
Attacks that exploit this kind of access
logbook_query. It is categorised as a Read tool in the Homeassistant MCP Server, which means it retrieves data without modifying state.
Register the Homeassistant MCP server in PolicyLayer and add a rule for logbook_query: 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 Homeassistant. Nothing to install.
logbook_query 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 logbook_query 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 logbook_query. 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.
logbook_query is provided by the Homeassistant MCP server (robbrad/homeassistant-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 →