ligolo_interface_create · Ligolo-ng MCP Server MCP

WHAT IT DOES

What ligolo_interface_create does on Ligolo-ng MCP Server

AI agents invoke ligolo_interface_create 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_interface_create needs a policy

Creating a TUN (network tunnel) interface is a privileged system-level operation that modifies the host's network configuration. It runs a kernel-level operation to instantiate a virtual network device, enabling network pivoting capabilities.

From the tool's definition Create a TUN interface for ligolo-ng tunneling

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ligolo_interface_create Rate-limited

ligolo_interface_create 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_interface_create": {
      "limits": [
        {
          "counter": "ligolo_interface_create_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_interface_create

What does the ligolo_interface_create tool do? +

Create a TUN interface for ligolo-ng tunneling. 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_interface_create? +

Register the Ligolo-ng MCP Server MCP server in PolicyLayer and add a rule for ligolo_interface_create: 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_interface_create? +

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

Can I rate-limit ligolo_interface_create? +

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

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

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