Get EV Charging Station status by connecting directly to the EVCS device (not through the GX). Reads charger status, power per phase, charging current, session energy, mode, phase configuration, temperatures, and errors. The host parameter should be the EVCS IP address (not the GX). For EV charge...
AI agents call victron_evcs_status to retrieve information from Victron Tcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only operations on EV charging station devices, retrieving telemetry and status information without side effects. It aligns with the 'Read' category definition: retrieves or queries data with no side effects. The low severity reflects minimal blast radius from misuse—an AI agent reading charger data cannot damage systems or create financial obligations.
From the tool's definition Tool description states it 'Reads charger status, power per phase, charging current, session energy, mode, phase configuration, temperatures, and errors' and explicitly instructs to 'Get EV Charging Station status' with no modification, deletion, or execution…
Attacks that exploit this kind of access
Get EV Charging Station status by connecting directly to the EVCS device (not through the GX). Reads charger status, power per phase, charging current, session energy, mode, phase configuration, temperatures, and errors. The host parameter should be the EVCS IP address (not the GX). For EV charger data proxied through the GX device, use victron_read_category with category. It is categorised as a Read tool in the Victron Tcp MCP Server, which means it retrieves data without modifying state.
Register the Victron Tcp MCP server in PolicyLayer and add a rule for victron_evcs_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 Victron Tcp. Nothing to install.
victron_evcs_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 victron_evcs_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 victron_evcs_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.
victron_evcs_status is provided by the Victron Tcp MCP server (lubosstrejcek/victron-tcp). 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 →