get_state_history

Get state history for an entity over the last N hours.

SERVERHa Nexus Agent SOURCEfistacho/ha-nexus-agent
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about get_state_history

What does the get_state_history tool do? +

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.

How do I enforce a policy on get_state_history? +

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.

What risk level is get_state_history? +

get_state_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_state_history? +

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.

How do I block get_state_history completely? +

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.

What MCP server provides get_state_history? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ha Nexus Agent's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.