AI agents call get_history 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 appears to query historical records from Home Assistant (device states, events, or sensor data over time). No description provided, but the name, sibling tools, and server context strongly suggest a read-only retrieval operation. Retrieving historical data has minimal blast radius—an AI agent cannot cause harm by querying logs or past states.
From the tool's definition Tool name 'get_history' and context as a sibling to 'get_history_range', 'get_statistics', and read-only query tools like 'get_entity' and 'get_entities_by_area'. The pattern and naming convention indicate this retrieves historical data without modification.
Documented attack patterns abuse exactly the kind of access get_history 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 get_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_history": {}
}
}get_history 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_history. 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 get_history: 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.
get_history 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_history 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_history. 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_history 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.