Delete a route from the routing table
AI agents call ligolo_route_delete to permanently remove resources in Ligolo-ng MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a route from a routing table is an irreversible destructive action. Once deleted, the route is gone and network traffic patterns are altered. In the context of Ligolo-ng (a network pivoting tool used during security assessments), deleting routes can break established tunnels and pivoting paths, disrupting ongoing operations.
From the tool's definition Tool name contains 'delete' and description states 'Delete a route from the routing table' — this irreversibly removes routing configuration.
Attacks that exploit this kind of access
Delete a route from the routing table. It is categorised as a Destructive tool in the Ligolo-ng MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ligolo-ng MCP Server MCP server in PolicyLayer and add a rule for ligolo_route_delete: 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_route_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ligolo_route_delete 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_route_delete. 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_route_delete 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 →