Current grid status (connected / off-grid) for the system.
AI agents call get_grid_status 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 queries the current grid connection state, returning status information without modifying, executing, or destructively affecting any system. It is a straightforward read operation consistent with the server's stated read-only access model for solar production and system telemetry.
From the tool's definition Tool name 'get_grid_status' and description 'Current grid status (connected / off-grid) for the system' indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Current grid status (connected / off-grid) for the system. 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_grid_status: 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_grid_status 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_grid_status 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_grid_status. 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_grid_status 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 →