get_state_history
Get state history for an entity over the last N hours.
This record as markdown: /tools/fistacho-ha-nexus-agent/get-state-history.md
What get_state_history does on Ha Nexus Agent
AI agents call get_state_history to retrieve information from Ha Nexus Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_state_history is rated Low
This tool retrieves time-series data about entity states from Home Assistant's history database. It has no side effects—it only reads and returns information. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an attacker could learn historical patterns of home activity but cannot control devices or change system state.
From the tool's definition Tool name 'get_state_history' and description 'Get state history for an entity over the last N hours' indicate a query operation that retrieves historical state data without modifying, deleting, or executing actions.
Attacks that exploit this kind of access
The rule that runs get_state_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ha Nexus Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_state_history, this is the rule to start with:
get_state_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every get_state_history call is checked against it from then on.
Questions about get_state_history
Get state history for an entity over the last N hours. It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for get_state_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 Ha Nexus Agent. Nothing to install.
get_state_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_state_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_state_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_state_history is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ha Nexus Agent, and thousands of servers like it.
This server
Across the catalogue