get_last_power_data
AI agents call get_last_power_data to retrieve information from Alpha ESS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix is a strong indicator of read-only retrieval. The description is empty, but the naming convention combined with context from sibling tools that retrieve monitoring data (energy statistics, power data, configuration snapshots) strongly suggests this tool queries recent power data from the inverter/battery system without modifying any state.
From the tool's definition Tool name 'get_last_power_data' uses the 'get' verb, which indicates retrieval of data. The sibling tools on this server include 'get_alpha_ess_data', 'get_charge_config', 'get_discharge_config', 'get_ess_list', 'get_one_date_energy_data', and…
Attacks that exploit this kind of access
get_last_power_data. It is categorised as a Read tool in the Alpha ESS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Alpha ESS MCP Server MCP server in PolicyLayer and add a rule for get_last_power_data: 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 Alpha ESS MCP Server. Nothing to install.
get_last_power_data 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_last_power_data 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_last_power_data. 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_last_power_data is provided by the Alpha ESS MCP Server MCP server (michaelkrasa/alpha-ess-mcp-server). 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 →