High Risk →

power_on_range

Power on all VMs in the range. Args: user_id: Optional user ID (admin only) Returns: Power on result

How to control power_on_range ↓

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.

High Risk

This tool triggers an external operation (powering on virtual machines) that changes the state of infrastructure in the cyber range. It is an Execute-category action because it initiates system operations on multiple VMs. Misuse could inadvertently activate unintended or malicious range environments, but the action is reversible (VMs can be powered off), so it does not reach Destructive severity.

From the tool's definition Power on all VMs in the range

Risk signalsAdmin/system-level operation

Documented attack patterns abuse exactly the kind of access power_on_range 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 power_on_range:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "power_on_range": {
      "limits": [
        {
          "counter": "power_on_range_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

  1. Create a free account and register Ludus FastMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the power_on_range tool do? +

Power on all VMs in the range. Args: user_id: Optional user ID (admin only) Returns: Power on result. 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.

How do I enforce a policy on power_on_range? +

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.

What risk level is power_on_range? +

power_on_range is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit power_on_range? +

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.

How do I block power_on_range completely? +

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.

What MCP server provides power_on_range? +

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.

Enforce policy on every Ludus FastMCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.