System event log (faults, state changes, etc.) within a date range.
AI agents call get_events to retrieve information from Enphase Solar 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 historical event log data without modifying, deleting, or executing any operations. It is purely informational, querying past system events within a date range. The blast radius of misuse is minimal—an attacker could only gain visibility into system events, not alter system state or access sensitive operational controls like battery or EV charger settings.
From the tool's definition Tool name 'get_events' and description 'System event log (faults, state changes, etc.) within a date range' indicate a retrieval operation with no side effects. The server description explicitly states 'read-only access' for data retrieval tools.
Attacks that exploit this kind of access
System event log (faults, state changes, etc.) within a date range. It is categorised as a Read tool in the Enphase Solar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enphase Solar MCP Server MCP server in PolicyLayer and add a rule for get_events: 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 Enphase Solar MCP Server. Nothing to install.
get_events 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_events 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_events. 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_events is provided by the Enphase Solar MCP Server MCP server (xianman/enphase-mcp). 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 →