PRIMARY RANGE ORCHESTRATOR - Use this FIRST for any range creation! Analyzes requirements, researches roles/templates, designs VM architecture, generates structured instructions using existing MCP tools, and estimates resource requirements.
AI agents use ludus_range_planner 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.
An AI agent can call ludus_range_planner faster than any human can review — one bad instruction and it creates or modifies resources in LudusMCP Server by the hundred, each call as confident as the last.
Documented attack patterns abuse exactly the kind of access ludus_range_planner 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 ludus_range_planner:
{
"version": "1",
"default": "deny",
"tools": {
"ludus_range_planner": {
"limits": [
{
"counter": "ludus_range_planner_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ludus_range_planner 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.
PRIMARY RANGE ORCHESTRATOR - Use this FIRST for any range creation! Analyzes requirements, researches roles/templates, designs VM architecture, generates structured instructions using existing MCP tools, and estimates resource requirements. 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 ludus_range_planner: 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.
ludus_range_planner 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 ludus_range_planner 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 ludus_range_planner. 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.
ludus_range_planner 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.