Get current status of a Powerwall/Solar system (battery level, power flow, grid status)
AI agents call get_live_status 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 only queries and retrieves real-time monitoring data from a Powerwall/Solar system. It has no side effects, does not execute commands, modify settings, or control devices. It is a straightforward information retrieval operation, consistent with other Read-category monitoring tools on this server (get_device_status, get_events, etc.).
From the tool's definition Tool name is 'get_live_status' and description states it retrieves current status information (battery level, power flow, grid status) with no modification or control capability mentioned.
Attacks that exploit this kind of access
Get current status of a Powerwall/Solar system (battery level, power flow, grid status). 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_live_status: 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_live_status 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_live_status 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_live_status. 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_live_status 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 →