ligolo_route_add · Ligolo-ng MCP Server MCP: Risk & Policy

WHAT IT DOES

What ligolo_route_add does on Ligolo-ng MCP Server

AI agents invoke ligolo_route_add 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_route_add needs a policy

Adding a network route is an active network configuration change that enables traffic to flow through a pivot/tunnel to otherwise inaccessible network segments. In the context of a penetration testing pivot tool (Ligolo-ng), this operation establishes new network paths on the host system, which is an Execute-level action with high blast radius since it can expose internal network segments to the AI agent's reach.

From the tool's definition 'Add a route to access the agent' — modifies network routing configuration to enable tunneled access through Ligolo-ng pivoting infrastructure

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ligolo_route_add Rate-limited

ligolo_route_add 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_route_add": {
      "limits": [
        {
          "counter": "ligolo_route_add_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_route_add

What does the ligolo_route_add tool do? +

Add a route to access the agent. 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_route_add? +

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

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

Can I rate-limit ligolo_route_add? +

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

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

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