set_battery_charge
AI agents use set_battery_charge to create or update resources in Alpha ESS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Alpha ESS MCP Server environment.
Based on the tool name and server context, this tool likely configures battery charging schedules or parameters on a physical energy storage system. This is a Write operation (modifying configuration), but it has high severity since misconfiguration of battery charging on a real solar/battery system could cause physical damage or energy waste.
From the tool's definition Tool name 'set_battery_charge' implies writing/modifying battery charge configuration; description is empty and uninformative
Attacks that exploit this kind of access
set_battery_charge. It is categorised as a Write tool in the Alpha ESS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Alpha ESS MCP Server MCP server in PolicyLayer and add a rule for set_battery_charge: 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.
set_battery_charge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_battery_charge 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 set_battery_charge. 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.
set_battery_charge 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 →