Build a range configuration from a natural language prompt. Args: prompt: Natural language description of desired range auto_deploy: Automatically deploy after building configuration user_id: Optional user ID (admin only) Returns: Generated configuration and deployment result if auto_deploy=True
AI agents invoke build_range_from_prompt to trigger actions in Ludus FastMCP. 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.
This tool executes dynamic infrastructure operations based on user input. While the core action of 'building a configuration' from a prompt is generative, the auto_deploy capability means it can trigger range deployment—an operation that provisions and starts cyber range environments. The effects are externally consequential and dependent on the natural language prompt argument.
From the tool's definition Tool builds and optionally auto-deploys range configurations from natural language prompts. The description states it can 'Automatically deploy after building configuration', which triggers external operations (range deployment) whose effects depend on the…
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access build_range_from_prompt 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 build_range_from_prompt:
{
"version": "1",
"default": "deny",
"tools": {
"build_range_from_prompt": {
"limits": [
{
"counter": "build_range_from_prompt_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}build_range_from_prompt 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.
Build a range configuration from a natural language prompt. Args: prompt: Natural language description of desired range auto_deploy: Automatically deploy after building configuration user_id: Optional user ID (admin only) Returns: Generated configuration and deployment result if auto_deploy=True. It is categorised as a Execute tool in the Ludus FastMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for build_range_from_prompt: 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.
build_range_from_prompt 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 build_range_from_prompt 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 build_range_from_prompt. 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.
build_range_from_prompt 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.