List all TUN interfaces on Kali
AI agents call ligolo_interface_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 performs a simple enumeration of existing TUN (tunnel) interfaces on the system. It has no side effects, does not execute commands, does not modify configuration, and does not delete resources. The action is purely informational retrieval, fitting the 'Read' category.
From the tool's definition Tool name 'ligolo_interface_list' and description 'List all TUN interfaces on Kali' indicate a read-only query operation that retrieves interface information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List all TUN interfaces on Kali. 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_interface_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_interface_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_interface_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_interface_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_interface_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 →