Abort any active deployment and then remove the range. This is a convenience function that combines abort_range_deployment() and delete_range(). Equivalent to running: 1. ludus range abort 2. ludus rm (with confirmation) Args: confirm: Confirmation flag (must be True to proceed) user_id: Optional...
AI agents call abort_and_remove_range to permanently remove resources in Ludus FastMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of cyber range environments. While the confirmation flag and optional user_id restrictions provide some safeguards, the core function destroys infrastructure that cannot be trivially recovered. The high blast radius comes from the potential to delete active deployments and their associated data in a production cyber range environment.
From the tool's definition Tool description states it 'Abort any active deployment and then remove the range' and is 'Equivalent to running: 1. ludus range abort 2. ludus rm (with confirmation)'.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access abort_and_remove_range gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ludus FastMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for abort_and_remove_range:
{
"version": "1",
"default": "deny",
"hide": [
"abort_and_remove_range"
]
}abort_and_remove_range disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Abort any active deployment and then remove the range. This is a convenience function that combines abort_range_deployment() and delete_range(). Equivalent to running: 1. ludus range abort 2. ludus rm (with confirmation) Args: confirm: Confirmation flag (must be True to proceed) user_id: Optional user ID (admin only) Returns: Combined abort and deletion results Example: # Abort and remove current user's range result = await abort_and_remove_range(confirm=True). It is categorised as a Destructive tool in the Ludus FastMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for abort_and_remove_range: 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 Ludus FastMCP. Nothing to install.
abort_and_remove_range 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 abort_and_remove_range 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 abort_and_remove_range. 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.
abort_and_remove_range is provided by the Ludus Fast MCP server (tjnull/ludus-fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 201 Ludus FastMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
201 Ludus FastMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.