AI agents use clone_and_modify_scenario 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.
Cloning and modifying scenarios in a cyber range creates or alters test configurations that could affect security testing environments, research workflows, and potentially training data. This is a Write action (reversible modification), not Destructive (no deletion), but elevated to 'high' severity because misuse could corrupt or sabotage range scenarios used for security research.
From the tool's definition Tool name 'clone_and_modify_scenario' indicates creation/modification of scenario data. Context shows this is a cyber range management system where scenarios are core operational entities.
Documented attack patterns abuse exactly the kind of access clone_and_modify_scenario 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_and_modify_scenario:
{
"version": "1",
"default": "deny",
"tools": {
"clone_and_modify_scenario": {
"limits": [
{
"counter": "clone_and_modify_scenario_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}clone_and_modify_scenario 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.
Free to start. No card required.
clone_and_modify_scenario. 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_and_modify_scenario: 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_and_modify_scenario 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_and_modify_scenario 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_and_modify_scenario. 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_and_modify_scenario 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.
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.