ligolo_tunnel_start · Ligolo-ng MCP Server MCP

WHAT IT DOES

What ligolo_tunnel_start does on Ligolo-ng MCP Server

AI agents invoke ligolo_tunnel_start to trigger actions in Ligolo-ng MCP Server. 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 ligolo_tunnel_start needs a policy

This tool triggers an active network operation (tunnel initialization) rather than merely querying state. While not destructive or financial, it executes external operations that can redirect traffic and expose network infrastructure. The blast radius is high because a misconfigured or malicious tunnel could pivot an attacker deeper into a compromised network, exfiltrate data, or enable lateral movement.

From the tool's definition Tool name 'ligolo_tunnel_start' and description 'Start a tunnel through a selected agent session' indicate activation of network tunneling operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ligolo_tunnel_start Rate-limited

ligolo_tunnel_start 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": {
    "ligolo_tunnel_start": {
      "limits": [
        {
          "counter": "ligolo_tunnel_start_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 Ligolo-ng MCP Server, so you can run agents against it safely.

FAQ

Questions about ligolo_tunnel_start

What does the ligolo_tunnel_start tool do? +

Start a tunnel through a selected agent session. It is categorised as a Execute tool in the Ligolo-ng MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ligolo_tunnel_start? +

Register the Ligolo-ng MCP Server MCP server in PolicyLayer and add a rule for ligolo_tunnel_start: 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 Ligolo-ng MCP Server. Nothing to install.

What risk level is ligolo_tunnel_start? +

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

Can I rate-limit ligolo_tunnel_start? +

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

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

ligolo_tunnel_start is provided by the Ligolo-ng MCP Server MCP server (schwarztim/sec-ligolo-ng-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.