Configured charging schedules for an Enphase IQ EV charger.
AI agents call get_ev_charger_schedules 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 existing schedule configuration data from an EV charger. It performs no data modification, deletion, or execution of commands—merely querying the current state of charging schedules. The blast radius of misuse is minimal; an attacker could only gain visibility into when an EV charger is scheduled to operate, which is low-sensitivity operational data.
From the tool's definition Tool name 'get_ev_charger_schedules' and description 'Configured charging schedules for an Enphase IQ EV charger' indicate a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
Configured charging schedules for an Enphase IQ EV charger. 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_ev_charger_schedules: 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_ev_charger_schedules 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_ev_charger_schedules 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_ev_charger_schedules. 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_ev_charger_schedules 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 →