Critical Risk →

cleanup_old_ranges

cleanup_old_ranges

How to control cleanup_old_ranges ↓

AI agents call cleanup_old_ranges 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.

Critical Risk

The word 'cleanup' strongly implies deletion or removal of old range environments. Given the context of sibling tools that abort and remove ranges, this tool likely irreversibly destroys cyber range infrastructure.

From the tool's definition Tool name 'cleanup_old_ranges' on a server with sibling tools like 'abort_and_remove_range' and 'abort_range_deployment'; 'cleanup' typically implies irreversible removal of resources.

Documented attack patterns abuse exactly the kind of access cleanup_old_ranges 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 cleanup_old_ranges:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cleanup_old_ranges"
  ]
}

cleanup_old_ranges disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Ludus FastMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the cleanup_old_ranges tool do? +

cleanup_old_ranges. 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.

How do I enforce a policy on cleanup_old_ranges? +

Register the Ludus Fast MCP server in PolicyLayer and add a rule for cleanup_old_ranges: 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.

What risk level is cleanup_old_ranges? +

cleanup_old_ranges is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cleanup_old_ranges? +

Yes. Add a rate_limit block to the cleanup_old_ranges 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.

How do I block cleanup_old_ranges completely? +

Set action: deny in the PolicyLayer policy for cleanup_old_ranges. 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.

What MCP server provides cleanup_old_ranges? +

cleanup_old_ranges 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.

Enforce policy on every Ludus FastMCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.