abort_and_remove_range
A destructive tool on the Ludus Fast MCP server.
This record as markdown: /tools/tjnull-ludus-fastmcp/abort-and-remove-range.md
What abort_and_remove_range does on Ludus FastMCP
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.
Why abort_and_remove_range is rated Critical
The term 'remove' in the context of range management implies irreversible deletion or destruction of cyber range resources. While the description is empty, the sibling tools include 'abort_range_deployment' (which aborts but may be reversible) and 'apply_blueprint_to_range' (which modifies), but this tool's explicit 'remove' designation suggests data deletion that cannot be undone.
From the tool's definition Tool name 'abort_and_remove_range' contains 'remove', indicating irreversible deletion of a cyber range environment. The word 'abort' combined with 'remove' suggests permanent termination and cleanup of range infrastructure.
Attacks that exploit this kind of access
The rule that runs abort_and_remove_range safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ludus FastMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For abort_and_remove_range, this is the rule to start with:
abort_and_remove_range is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ludus FastMCP, apply this rule, and every abort_and_remove_range call is checked against it from then on.
Questions about abort_and_remove_range
abort_and_remove_range is a destructive tool on the Ludus Fast MCP server. 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.
More on Ludus Fast, and thousands of servers like it.
Across the catalogue