Get alternator data from Wakespeed WS500, Arco Zeus, Revatek Altion, or other NMEA 2000 DC alternator regulators: battery voltage/current, auxiliary voltage, temperature, energy produced, engine/alternator RPM, field drive %, alarms, and state. Use victron_discover to find the unit ID.
AI agents call victron_alternator_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 pure data retrieval from Victron Energy alternator regulators via Modbus TCP/MQTT. It queries real-time status and measurements with no side effects. The blast radius of misuse is minimal—an AI agent could at worst spam read requests or log sensitive power system metrics, but cannot modify configurations, execute commands, delete data, or affect financial transactions.
From the tool's definition Tool description explicitly states 'Get alternator data' and lists only read operations: retrieving 'battery voltage/current, auxiliary voltage, temperature, energy produced, engine/alternator RPM, field drive %, alarms, and state.' No modification, deletion,…
Attacks that exploit this kind of access
Get alternator data from Wakespeed WS500, Arco Zeus, Revatek Altion, or other NMEA 2000 DC alternator regulators: battery voltage/current, auxiliary voltage, temperature, energy produced, engine/alternator RPM, field drive %, alarms, and state. Use victron_discover to find the unit ID. 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_alternator_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_alternator_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_alternator_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_alternator_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_alternator_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 →