delete_ranges_by_status
A destructive tool on the Ludus Fast MCP server.
This record as markdown: /tools/tjnull-ludus-fastmcp/delete-ranges-by-status.md
What delete_ranges_by_status does on Ludus FastMCP
AI agents call delete_ranges_by_status 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 delete_ranges_by_status is rated Critical
The tool name unambiguously indicates deletion of ranges (infrastructure or environment configurations) based on status criteria. In a cyber range management system, deleting ranges would permanently remove test environments, configurations, and associated data. This is irreversible and matches the Destructive category definition.
From the tool's definition Tool name 'delete_ranges_by_status' explicitly uses 'delete', which indicates irreversible data removal. The verb 'delete' is a core indicator of destructive operations that cannot be undone.
Attacks that exploit this kind of access
The rule that runs delete_ranges_by_status 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 delete_ranges_by_status, this is the rule to start with:
delete_ranges_by_status 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 delete_ranges_by_status call is checked against it from then on.
Questions about delete_ranges_by_status
delete_ranges_by_status 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 delete_ranges_by_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 Ludus FastMCP. Nothing to install.
delete_ranges_by_status 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 delete_ranges_by_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 delete_ranges_by_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.
delete_ranges_by_status 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