tunnel_start

What tunnel_start does on LocalAnt

AI agents invoke tunnel_start to trigger actions in LocalAnt. 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 tunnel_start is rated High

This tool triggers an external operation (starting a public tunnel) whose effects are significant and depend on gateway configuration. It enables network exposure of the LocalAnt gateway, potentially allowing remote access to the PC control capabilities. This is an Execute action because it initiates a process/service with real-world side effects, but not Destructive (reversible via tunnel_stop) and not Financial.

From the tool's definition Tool name 'tunnel_start' combined with description 'Start the public tunnel on the live gateway port' indicates initiation of a network tunnel that exposes a local service to the public internet.

The rule that runs tunnel_start safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tunnel_start, this is the rule to start with:

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

Questions about tunnel_start