ligolo_session_select · Ligolo-ng MCP Server MCP

WHAT IT DOES

What ligolo_session_select does on Ligolo-ng MCP Server

AI agents invoke ligolo_session_select 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_session_select needs a policy

Selecting a session in a network pivoting framework like Ligolo-ng is not a passive read operation; it sets operational state that controls which compromised agent subsequent commands (tunneling, routing, listeners) target. In a security assessment context this has high blast radius as it determines the pivot point for all subsequent network operations.

From the tool's definition 'Select an agent session to work with' — actively sets the active session context for a network pivoting proxy tool (Ligolo-ng), directing subsequent operations (tunnel creation, route manipulation, listener management) to a specific compromised agent

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ligolo_session_select Rate-limited

ligolo_session_select 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_session_select": {
      "limits": [
        {
          "counter": "ligolo_session_select_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_session_select

What does the ligolo_session_select tool do? +

Select an agent session to work with. 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_session_select? +

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

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

Can I rate-limit ligolo_session_select? +

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

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

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