victron_setup · Victron Tcp MCP: Risk & Policy

WHAT IT DOES

What victron_setup does on Victron Tcp

AI agents use victron_setup to create or update resources in Victron Tcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Victron Tcp environment.

WHY IT NEEDS A POLICY

Why victron_setup needs a policy

The tool's core functions include testing connectivity and discovering devices (Read-like behaviors), but the 'setup' and 'configuration generation' aspects indicate it creates or modifies system configuration state. This makes it Write rather than Read. It is not Destructive because setup operations are reversible.

From the tool's definition The tool performs 'Complete system setup and discovery' and 'generates ready-to-use MCP server configuration,' which involves creating or modifying configuration state on the Victron GX device.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

victron_setup Rate-limited

victron_setup stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_setup": {
      "limits": [
        {
          "counter": "victron_setup_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_setup

What does the victron_setup tool do? +

Complete system setup and discovery for a Victron GX device. Tests both Modbus TCP and MQTT connectivity, discovers all connected devices and services, recommends the best transport, and generates ready-to-use MCP server configuration. Use this as the first step after finding a device with victron_network_scan, or directly if you already know the host IP. It is categorised as a Write tool in the Victron Tcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on victron_setup? +

Register the Victron Tcp MCP server in PolicyLayer and add a rule for victron_setup: 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_setup? +

victron_setup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit victron_setup? +

Yes. Add a rate_limit block to the victron_setup 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_setup completely? +

Set action: deny in the PolicyLayer policy for victron_setup. 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_setup? +

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