get_discharge_config
AI agents call get_discharge_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.
This tool retrieves battery discharge configuration settings from the Alpha ESS system. Reading configuration data has no side effects, is non-destructive, and presents no financial or execution risk. The severity is low because the blast radius of exposing discharge configuration data (settings/parameters) is minimal—an AI agent obtaining this data cannot directly alter system behavior or cause damage.
From the tool's definition Tool name 'get_discharge_config' follows the read-only pattern (get_*) consistent with other tools on this server like 'get_charge_config', 'get_alpha_ess_data', 'get_last_power_data', and 'get_one_date_energy_data'.
Attacks that exploit this kind of access
get_discharge_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_discharge_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_discharge_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_discharge_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_discharge_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_discharge_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 →