victron_generator_status · Victron Tcp MCP: Risk & Policy

WHAT IT DOES

What victron_generator_status does on Victron Tcp

AI agents invoke victron_generator_status to trigger actions in Victron Tcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why victron_generator_status needs a policy

While the tool reads status information, the description explicitly states it includes a 'manual start/stop command' and 'controls' the generator start/stop logic via GX relay. Issuing start/stop commands to a physical generator is an external operation with real-world consequences (starting/stopping electrical generation equipment), placing this firmly in the Execute category.

From the tool's definition 'manual start/stop command' and 'controls the GX relay-based generator start/stop logic'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

victron_generator_status Rate-limited

victron_generator_status stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "victron_generator_status": {
      "limits": [
        {
          "counter": "victron_generator_status_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Victron Tcp, so you can run agents against it safely.

FAQ

Questions about victron_generator_status

What does the victron_generator_status tool do? +

Get GX generator auto start/stop status and control: manual start/stop command, start condition (SOC/load/voltage/manual), runtime, quiet hours, start/stop state, auto start enabled, service countdown, and alarms. This controls the GX relay-based generator start/stop logic. Unit ID is always 100. It is categorised as a Execute tool in the Victron Tcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on victron_generator_status? +

Register the Victron Tcp MCP server in PolicyLayer and add a rule for victron_generator_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.

What risk level is victron_generator_status? +

victron_generator_status is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit victron_generator_status? +

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

How do I block victron_generator_status completely? +

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

What MCP server provides victron_generator_status? +

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