This record as markdown: /tools/tjnull-ludus-fastmcp/power-on-range.md
What power_on_range does on Ludus FastMCP
AI agents invoke power_on_range 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.
Why power_on_range is rated High
This tool triggers an external operation that starts all virtual machines in a cyber range environment. It has significant blast radius as powering on an entire range could activate malicious or resource-intensive workloads, consume substantial compute resources, and initiate network activity across all VMs simultaneously.
From the tool's definition Power on all VMs in the range
Attacks that exploit this kind of access
The rule that runs power_on_range safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ludus FastMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For power_on_range, this is the rule to start with:
power_on_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ludus FastMCP, apply this rule, and every power_on_range call is checked against it from then on.
Questions about power_on_range
Power on all VMs in the range. 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 power_on_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 Ludus FastMCP. Nothing to install.
power_on_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 power_on_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 power_on_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.
power_on_range 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.
More on Ludus Fast, and thousands of servers like it.
Across the catalogue