Get standalone inverter data (Phoenix, Inverter RS, VE.Direct inverters): AC output voltage, current, power, frequency, state, and alarms. This is for standalone inverters — for Multi/Quattro, use victron_vebus_status instead.
AI agents call victron_inverter_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 only reads and queries inverter status information from Victron Energy systems. It has no capability to modify settings, execute commands, delete data, or trigger external operations. The data retrieved (voltage, current, power, frequency, state, alarms) are all monitoring metrics with no side effects. This is a straightforward read operation with minimal risk of harm even if misused by an AI agent.
From the tool's definition Tool retrieves real-time inverter status data including AC output voltage, current, power, frequency, state, and alarms. The description explicitly states it 'Get[s]' data with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get standalone inverter data (Phoenix, Inverter RS, VE.Direct inverters): AC output voltage, current, power, frequency, state, and alarms. This is for standalone inverters — for Multi/Quattro, use victron_vebus_status instead. 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_inverter_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_inverter_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_inverter_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_inverter_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_inverter_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 →