Medium Risk

clone_range

Clone the current range to another user. Args: target_user_id: User ID to clone range to include_snapshots: Whether to include snapshots in clone user_id: Optional user ID (admin only) Returns: Clone operation result

How to control clone_range ↓

AI agents use clone_range to create or update resources in Ludus FastMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ludus FastMCP environment.

Medium Risk

Cloning a range creates a new copy of the environment for another user — a reversible write/create operation. However, it has a high blast radius because it duplicates potentially large cyber range environments to arbitrary users, and with include_snapshots it copies full VM state.

From the tool's definition Clone the current range to another user

Risk signalsAdmin/system-level operation

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "clone_range": {
      "limits": [
        {
          "counter": "clone_range_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

clone_range stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  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.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the clone_range tool do? +

Clone the current range to another user. Args: target_user_id: User ID to clone range to include_snapshots: Whether to include snapshots in clone user_id: Optional user ID (admin only) Returns: Clone operation result. It is categorised as a Write tool in the Ludus FastMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on clone_range? +

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

What risk level is clone_range? +

clone_range is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit clone_range? +

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

How do I block clone_range completely? +

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

What MCP server provides clone_range? +

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

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.