tunnel_stop

What tunnel_stop does on LocalAnt

AI agents invoke tunnel_stop 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_stop is rated High

Stopping a tunnel is an Execute action—it triggers an external operation (terminating a tunnel process) whose effects depend on which tunnel is running. It is not Read (no data retrieval), Write (not creating/modifying reversible data), Destructive (the tunnel can be restarted), or Financial. Severity is medium because stopping a tunnel disrupts connectivity but does not destroy data or cause financial harm.

From the tool's definition Tool name 'tunnel_stop' and description 'Stop the public tunnel' indicate termination of an active network tunnel service. This is an operational action that affects system state and network connectivity.

The rule that runs tunnel_stop 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_stop, this is the rule to start with:

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

Questions about tunnel_stop