wakeonlan_node

Send a Wake-on-LAN magic packet to a node.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gethosthewalrus-proxmox-mcp/wakeonlan-node.md

WHAT IT DOES

What wakeonlan_node does on Proxmox MCP Server

AI agents invoke wakeonlan_node to trigger actions in Proxmox MCP Server. 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.

RISK

Why wakeonlan_node is rated High

This tool triggers an external network operation (sending a WoL magic packet) that causes a physical or virtual node to power on. It executes an action with real-world side effects (powering on infrastructure nodes), but is not destructive, financial, or a simple data read/write. The blast radius is medium since it could inadvertently power on nodes in a managed environment.

From the tool's definition Send a Wake-on-LAN magic packet to a node

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wakeonlan_node safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wakeonlan_node, this is the rule to start with:

wakeonlan_node Rate-limited

wakeonlan_node 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wakeonlan_node": {
      "limits": [
        {
          "counter": "wakeonlan_node_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every wakeonlan_node call is checked against it from then on.

FAQ

Questions about wakeonlan_node

What does the wakeonlan_node tool do? +

Send a Wake-on-LAN magic packet to a node. It is categorised as a Execute tool in the Proxmox MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wakeonlan_node? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for wakeonlan_node: 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 Proxmox MCP Server. Nothing to install.

What risk level is wakeonlan_node? +

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

Can I rate-limit wakeonlan_node? +

Yes. Add a rate_limit block to the wakeonlan_node 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 wakeonlan_node completely? +

Set action: deny in the PolicyLayer policy for wakeonlan_node. 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 wakeonlan_node? +

wakeonlan_node is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Proxmox MCP Server, and thousands of servers like it.

This server

All 286 Proxmox MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →