New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

abort_range_deployment

A destructive tool on the Ludus Fast MCP server.

SERVERLudus FastMCP SOURCEtjnull/ludus-fastmcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tjnull-ludus-fastmcp/abort-range-deployment.md

What abort_range_deployment does on Ludus FastMCP

AI agents call abort_range_deployment 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_range_deployment is rated Critical

The tool name contains 'abort', which in the context of this server (cyber range management) strongly implies irreversible cancellation of a deployment operation. While aborting a deployment may be less severe than deleting a range outright, it can leave infrastructure in an inconsistent or unrecoverable state.

From the tool's definition Tool name 'abort_range_deployment' — 'abort' implies stopping/cancelling an in-progress deployment, likely irreversibly terminating the deployment process.

Questions about abort_range_deployment

What does the abort_range_deployment tool do? +

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

How do I enforce a policy on abort_range_deployment? +

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

abort_range_deployment 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 abort_range_deployment? +

Yes. Add a rate_limit block to the abort_range_deployment 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 abort_range_deployment completely? +

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ludus Fast's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.