List all connected agents to the ligolo-ng proxy
AI agents call ligolo_agents_list to retrieve information from Ligolo-ng MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about connected agents without creating, modifying, deleting, or executing operations. However, the information retrieved (active agents in a network pivoting tool) could enable an attacker to map compromised infrastructure, justifying medium severity despite the read-only nature. The confidence is high because the intent is unambiguous.
From the tool's definition Tool name is 'ligolo_agents_list' and description states it 'List all connected agents to the ligolo-ng proxy' — a retrieval operation with no data modification.
Attacks that exploit this kind of access
List all connected agents to the ligolo-ng proxy. It is categorised as a Read tool in the Ligolo-ng MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ligolo-ng MCP Server MCP server in PolicyLayer and add a rule for ligolo_agents_list: 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.
ligolo_agents_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ligolo_agents_list 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.
Set action: deny in the PolicyLayer policy for ligolo_agents_list. 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.
ligolo_agents_list 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →