Ligolo-ng MCP Server

ligolo_send_command

Send raw commands to the Ligolo-ng proxy console to execute advanced network pivoting operations.

Instructions

Send a raw command to the ligolo-ng proxy console (advanced)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "ligolo_send_command"
  }
}

Input Schema

Name	Required	Description	Default
`command`	Yes	Raw command to send to ligolo-ng console

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 26, 2026

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description must disclose behavioral traits. It only says 'raw command' and 'advanced' without mentioning potential risks, side effects, or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, 10 words, front-loaded with key information. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is simple with one param and no output schema. Description covers the core action but lacks details on return values, error conditions, or behavior on invalid commands.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the parameter description already explains the param. The tool description adds the word 'advanced' but no additional semantic value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (send) and resource (ligolo-ng proxy console), and uses 'advanced' to hint at caution. However, it does not explicitly differentiate from similar sibling tools like ligolo_agent_command.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like ligolo_agent_command. The word 'advanced' implies limited use but does not provide concrete criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.