List all Enphase systems associated with the developer account.
AI agents call get_systems 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 or queries system information without creating, modifying, deleting, or executing any operations. It is a straightforward enumeration of existing data associated with the account. Blast radius is minimal—an AI agent using this tool can only discover what systems exist, not alter them or trigger actions. The lack of destructive, financial, or execution capability keeps severity low.
From the tool's definition Tool name 'get_systems' and description 'List all Enphase systems associated with the developer account' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all Enphase systems associated with the developer account. 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_systems: 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_systems 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_systems 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_systems. 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_systems 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 →