Check the status of the ligolo-ng proxy server
AI agents call ligolo_proxy_status 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 pure read operation—it queries the status of an existing proxy service and returns informational data. There are no side effects, no data modifications, no code execution, and no destructive actions. The minimal blast radius (information disclosure) and read-only nature classify it as Read with low severity.
From the tool's definition Tool name 'ligolo_proxy_status' and description 'Check the status of the ligolo-ng proxy server' indicate a query operation that retrieves current state information without modifying or executing anything.
Attacks that exploit this kind of access
Check the status of the ligolo-ng proxy server. 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_proxy_status: 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_proxy_status 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_proxy_status 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_proxy_status. 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_proxy_status 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 →