get_charge_config
AI agents call get_charge_config 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 strongly suggests this tool retrieves or queries configuration data without modifying it. While the description is empty, the naming convention and context of sibling tools (set_battery_charge, set_battery_discharge) confirm this is a read operation that returns charge configuration. No data modification, deletion, code execution, or financial impact is expected.
From the tool's definition Tool name 'get_charge_config' indicates a retrieval operation ('get'). The sibling tools include 'set_battery_charge' and 'set_battery_discharge' which are the write operations; 'get_charge_config' is the read counterpart.
Attacks that exploit this kind of access
get_charge_config. 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_charge_config: 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_charge_config 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_charge_config 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_charge_config. 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_charge_config 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 →