get_ev_charger_telemetry

Interval energy telemetry for an Enphase IQ EV charger.

Server Enphase Solar MCP Server xianman/enphase-mcp
Category Read
Risk class Low
Parameters 00 required

What get_ev_charger_telemetry does on Enphase Solar MCP Server

AI agents call get_ev_charger_telemetry 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.

Why get_ev_charger_telemetry needs a policy

This tool purely retrieves telemetry data about EV charger operations. It queries historical or current energy data without creating, modifying, or deleting anything. The blast radius of misuse is minimal—an attacker could learn energy consumption patterns or charging schedules but cannot control the charger, move money, or cause harm. The 'get_' prefix and passive data retrieval nature confirm Read category.

From the tool's definition Tool name starts with 'get_' and description states it retrieves 'interval energy telemetry' with no mention of modification, deletion, or side effects. The server description confirms this is a 'read-only access' tool for solar/battery/EV data.

Questions about get_ev_charger_telemetry

What does the get_ev_charger_telemetry tool do? +

Interval energy telemetry 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.

How do I enforce a policy on get_ev_charger_telemetry? +

Register the Enphase Solar MCP Server MCP server in PolicyLayer and add a rule for get_ev_charger_telemetry: 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.

What risk level is get_ev_charger_telemetry? +

get_ev_charger_telemetry is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_ev_charger_telemetry? +

Yes. Add a rate_limit block to the get_ev_charger_telemetry 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.

How do I block get_ev_charger_telemetry completely? +

Set action: deny in the PolicyLayer policy for get_ev_charger_telemetry. 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.

What MCP server provides get_ev_charger_telemetry? +

get_ev_charger_telemetry 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.