Apply range configuration to Ludus server. Sets active configuration for deployment.\n\nWORKING DIRECTORY: All file paths are relative to ~/.ludus-mcp/range-config-templates/\n\nPATH USAGE: Use relative paths only (e.g.,
AI agents use set_range_config to create or update resources in LudusMCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LudusMCP Server environment.
The tool creates or modifies configuration state that affects deployed virtualized security training ranges. While it does not irreversibly delete data (which would be Destructive) or execute arbitrary code directly (Execute), it materially alters system configuration for training environments.
From the tool's definition Tool applies and sets active configuration for deployment to the Ludus server ('Sets active configuration for deployment'). This modifies the state of cybersecurity training environments through configuration changes.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access set_range_config 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 set_range_config:
{
"version": "1",
"default": "deny",
"tools": {
"set_range_config": {
"limits": [
{
"counter": "set_range_config_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_range_config 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.
Apply range configuration to Ludus server. Sets active configuration for deployment.\n\nWORKING DIRECTORY: All file paths are relative to ~/.ludus-mcp/range-config-templates/\n\nPATH USAGE: Use relative paths only (e.g.,. It is categorised as a Write tool in the LudusMCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LudusMCP Server MCP server in PolicyLayer and add a rule for set_range_config: 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.
set_range_config 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 set_range_config 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 set_range_config. 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.
set_range_config 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.