Get VE.Bus inverter/charger (Multi/Quattro) data: AC input/output voltage, current, power per phase, DC voltage, input current limit, mode, state, alarms, and ESS settings. Specify unitId for the VE.Bus device (check victron_discover to find it).
AI agents call victron_vebus_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 retrieves operational status and telemetry data from a VE.Bus device without any capability to modify settings, execute commands, or trigger actions. It is a read-only query of system state, consistent with sibling tools like victron_battery_status and victron_charger_status which all report monitoring data.
From the tool's definition Tool description states 'Get VE.Bus inverter/charger data' with metrics like voltage, current, power, mode, state, and alarms. No modification, deletion, or execution verbs present.
Attacks that exploit this kind of access
Get VE.Bus inverter/charger (Multi/Quattro) data: AC input/output voltage, current, power per phase, DC voltage, input current limit, mode, state, alarms, and ESS settings. Specify unitId for the VE.Bus device (check victron_discover to find it). 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_vebus_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_vebus_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_vebus_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_vebus_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_vebus_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 →