ligolo_agent_command · Ligolo-ng MCP Server MCP

WHAT IT DOES

What ligolo_agent_command does on Ligolo-ng MCP Server

AI agents invoke ligolo_agent_command 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_agent_command needs a policy

This tool generates commands that will be executed on target machines as part of a network security assessment. Execution of arbitrary commands on remote systems constitutes the Execute category.

From the tool's definition Tool name contains 'command' and description states it 'Generate the agent command to run on target machines'. This tool produces executable commands intended for remote execution during network pivoting operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ligolo_agent_command Rate-limited

ligolo_agent_command 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_agent_command": {
      "limits": [
        {
          "counter": "ligolo_agent_command_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_agent_command

What does the ligolo_agent_command tool do? +

Generate the agent command to run on target machines. 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_agent_command? +

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

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

Can I rate-limit ligolo_agent_command? +

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

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

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