This record as markdown: /tools/tjnull-ludus-fastmcp/clone-range.md
What clone_range does on Ludus FastMCP
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.
Why clone_range is rated Medium
Cloning a range creates a new copy of the environment and assigns it to another user. This is a Write operation (creates new data/resources). The severity is high because it duplicates potentially complex cyber range environments to another user's account, which could lead to unauthorized resource provisioning, privilege escalation scenarios, or exposing sensitive range configurations to unintended users.
From the tool's definition Clone the current range to another user
Attacks that exploit this kind of access
The rule that runs clone_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 clone_range, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ludus FastMCP, apply this rule, and every clone_range call is checked against it from then on.
Questions about clone_range
Clone the current range to another user. 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.
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.
clone_range is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on Ludus Fast, and thousands of servers like it.
This server
Across the catalogue