Deploy a Ludus range from a configuration file. This creates a new virtualized training environment based on the specified configuration. CREDENTIAL SECURITY REMINDER Ensure range configurations use credential placeholders: {{LudusCredName-<targetUser>-<credName>}} DO NOT deploy ranges with non-r...
AI agents invoke deploy_range to trigger actions in LudusMCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Deploying a range triggers external infrastructure provisioning — spinning up virtualized machines and networks. This is an Execute-category action because it runs external operations whose effects depend on the provided configuration arguments. It is not purely Write (data creation) since it executes complex orchestration and resource allocation.
From the tool's definition Deploy a Ludus range from a configuration file. This creates a new virtualized training environment based on the specified configuration.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access deploy_range gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LudusMCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deploy_range:
{
"version": "1",
"default": "deny",
"tools": {
"deploy_range": {
"limits": [
{
"counter": "deploy_range_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}deploy_range stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Deploy a Ludus range from a configuration file. This creates a new virtualized training environment based on the specified configuration. CREDENTIAL SECURITY REMINDER Ensure range configurations use credential placeholders: {{LudusCredName-<targetUser>-<credName>}} DO NOT deploy ranges with non-range-specific credentials such as API keys for external services, passwords not specific to the cyber range environment, or similar credentials embedded in config files! IMPORTANT LLM BEHAVIORAL PROMPTS: - SAFETY FIRST: Ludus operations can be destructive and time-consuming - VERIFY DESTRUCTIVE ACTIONS: Always confirm with user before destroy/delete operations - CHECK EXISTING STATE: Use list_user_ranges or get_range_status before major operations - DESTRUCTION IS PERMANENT: Destroying ranges deletes all VMs and data irreversibly - ADMIN vs USER: Admin operations (--user flag) affect other users. It is categorised as a Execute tool in the LudusMCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the LudusMCP Server MCP server in PolicyLayer and add a rule for deploy_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 LudusMCP Server. Nothing to install.
deploy_range is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deploy_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 deploy_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.
deploy_range is provided by the LudusMCP Server MCP server (noctedefensor/ludusmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 LudusMCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 LudusMCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.