Get list of registered Alpha ESS systems with auto-selection logic.
AI agents call get_ess_list 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 queries and returns a list of registered systems. It performs no data modification, deletion, code execution, or financial operations. The 'auto-selection logic' mentioned is a passive feature for selecting which system to query, not an action that changes state. This is a straightforward data retrieval operation, classifying as Read with low severity.
From the tool's definition Tool name 'get_ess_list' and description 'Get list of registered Alpha ESS systems' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get list of registered Alpha ESS systems with auto-selection logic. 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_ess_list: 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_ess_list 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_ess_list 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_ess_list. 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_ess_list 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 →