Skip to main content
Glama

deploy_scenario

Deploy fresh cyber range scenarios for security testing with optional SIEM integration, customization, or randomization. Automatically generates configurations without file uploads.

Instructions

Deploy a scenario with optional SIEM integration and customization.

IMPORTANT: This tool generates a FRESH configuration for each call. Each deployment builds a new scenario from scratch - no state is reused.

NO FILE UPLOAD REQUIRED: This tool automatically generates the configuration from the scenario parameters. You do NOT need to provide a config file or manual configuration.

CUSTOMIZATION AND RANDOMIZATION:

  • Use customize=True with custom parameters to deploy a customized scenario

  • Use randomize=True to deploy a randomized version with varied users/vulnerabilities

  • All customization parameters are optional - defaults used if not specified

Recommended Workflow:

  1. Use preview_scenario() first to verify what will be deployed

  2. (Optional) Abort any existing deployment: abort_range_deployment()

  3. (Optional) Delete existing range: delete_range(confirm=True)

  4. Deploy the scenario: deploy_scenario(scenario_key='redteam-lab-lite')

  5. Monitor progress: monitor_deployment() or quick_status()

Internal Workflow:

  1. Generates fresh scenario configuration based on parameters

  2. Applies customizations or randomization if requested

  3. Sets the configuration in Ludus (via PUT /range/config)

  4. Verifies the configuration was set correctly

  5. Starts deployment (via POST /range/deploy)

  6. Generates comprehensive walkthrough

  7. Returns deployment status, VM details, and walkthrough

Available scenarios:

  • redteam-lab-lite: 5 VMs (DC, 2 workstations, file server, Kali)

  • redteam-lab-intermediate: 10 VMs (DMZ, internal network, multiple servers)

  • redteam-lab-advanced: 21 VMs (2 forests with trust, DMZ, secure zone)

  • blueteam-lab-lite: 6 VMs (SOC with SIEM, detection)

  • blueteam-lab-intermediate: 11 VMs (SOC with EDR, IDS)

  • blueteam-lab-advanced: 21 VMs (Enterprise SOC, full stack)

  • purpleteam-lab-lite: 6 VMs (Red/Blue collaborative)

  • purpleteam-lab-intermediate: 10 VMs (Purple team with EDR)

  • purpleteam-lab-advanced: 13 VMs (Full SOC + adversary emulation)

  • malware-re-lab-lite: 3 VMs (Basic malware analysis)

  • malware-re-lab-intermediate: 7 VMs (Pro malware lab)

  • malware-re-lab-advanced: 18 VMs (Enterprise malware research)

  • wireless-lab: 2 VMs (WiFi pentesting)

Args: scenario_key: Scenario identifier (e.g., 'redteam-lab-lite') user_id: Optional user ID (admin only) ensure_roles: Ensure required Ansible roles are installed siem_type: SIEM type to include (wazuh, splunk, elastic, security-onion, none) resource_profile: Resource allocation profile (minimal, recommended, maximum) customize: Enable customization mode (use provided customizations) randomize: Enable randomization mode (generate random customizations) custom_users: List of custom user dicts with keys: username, password, display_name, groups (list), department (optional), title (optional), etc. vulnerability_config: Dict with keys like esc1_enabled, esc2_enabled, open_shares, etc. network_customizations: Dict with vlan_changes, additional_rules, remove_rules, etc. vm_customizations: Dict with vm_count_overrides, additional_vms, remove_vms, etc.

Returns: Deployment result with scenario details, VM list, deployment status, and walkthrough

Examples: # Simple deployment (default) deploy_scenario(scenario_key='redteam-lab-lite', siem_type='none')

# Randomized deployment
deploy_scenario(scenario_key='redteam-lab-lite', randomize=True)

# Custom users deployment
deploy_scenario(
    scenario_key='redteam-lab-lite',
    customize=True,
    custom_users=[
        {
            "username": "admin.user",
            "password": "CustomPass123!",
            "display_name": "Admin User",
            "groups": ["Domain Users", "Domain Admins"],
            "department": "IT"
        }
    ]
)

# Custom vulnerabilities
deploy_scenario(
    scenario_key='redteam-lab-lite',
    customize=True,
    vulnerability_config={
        "esc1_enabled": True,
        "esc8_enabled": True,
        "open_shares": True
    }
)

Natural Language Translation:

  • "Make a custom range using redteam-lab-lite" → customize=True

  • "Randomize redteam-lab-lite" → randomize=True

  • "Deploy with different users" → customize=True, custom_users=[...]

Note: For automated deployments with validation and monitoring, consider using smart_deploy() instead, which handles the full workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scenario_keyYes
user_idNo
ensure_rolesNo
siem_typeNowazuh
resource_profileNorecommended
customizeNo
randomizeNo
custom_usersNo
vulnerability_configNo
network_customizationsNo
vm_customizationsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: it generates fresh configurations with no state reuse, requires no file uploads, and outlines an internal workflow (e.g., configuration generation, PUT/POST operations). However, it lacks details on error handling, rate limits, or authentication requirements, which are important for a complex deployment tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with key information (purpose, important notes, customization details), but it is overly verbose with extensive lists (e.g., 13 scenario options) and redundant sections like 'Internal Workflow' and 'Natural Language Translation'. Some sentences, such as the detailed scenario list, could be trimmed or referenced externally without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (11 parameters, no annotations, but with an output schema), the description is largely complete. It covers purpose, usage, parameters, and behavioral context. The output schema handles return values, so the description appropriately focuses on deployment process and customization. Minor gaps include lack of error handling or security prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, so the description must compensate fully. It does so by providing detailed explanations for all 11 parameters, including lists of available scenarios (e.g., 'redteam-lab-lite'), SIEM types, and customization options. Examples and natural language translations further clarify parameter usage, adding significant value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Deploy a scenario with optional SIEM integration and customization.' It specifies the verb ('deploy') and resource ('scenario'), and distinguishes it from siblings like 'preview_scenario', 'abort_range_deployment', and 'smart_deploy' by detailing its unique role in generating fresh configurations and handling deployment workflows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool versus alternatives. It recommends using 'preview_scenario()' first, mentions 'abort_range_deployment()' and 'delete_range()' as optional preparatory steps, and advises considering 'smart_deploy()' for automated workflows. It also distinguishes usage based on customization needs (e.g., 'customize=True' vs. 'randomize=True').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tjnull/Ludus-FastMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server