Get historical energy data (solar production, battery usage, grid import/export)
AI agents call get_energy_history to retrieve information from Home Controller without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical energy consumption and production metrics without modifying any state or triggering actions. It is a straightforward data retrieval function with no side effects, blast radius is minimal, and the only risk is potential information disclosure of historical energy patterns.
From the tool's definition Tool name and description indicate retrieval of historical energy data: 'Get historical energy data (solar production, battery usage, grid import/export)'. No creation, modification, deletion, or side effects are described.
Attacks that exploit this kind of access
Get historical energy data (solar production, battery usage, grid import/export). It is categorised as a Read tool in the Home Controller MCP Server, which means it retrieves data without modifying state.
Register the Home Controller MCP server in PolicyLayer and add a rule for get_energy_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 Home Controller. Nothing to install.
get_energy_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_energy_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_energy_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_energy_history is provided by the Home Controller MCP server (winsthuang/home-controller). 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 →