wake_on_lan
Send a Wake-on-LAN magic packet to a MAC address.
This record as markdown: /tools/aaronckj-mcp-nettools/wake-on-lan.md
What wake_on_lan does on Mcp Nettools
AI agents invoke wake_on_lan to trigger actions in Mcp Nettools. 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 wake_on_lan is rated High
This tool triggers an external operation (sending a network packet) that causes a remote machine to power on. It is not merely reading data, nor is it destructive or financial. It executes an action with real-world side effects (waking/powering on hardware), making Execute the appropriate category. Severity is medium because misuse could power on unintended systems, but it is reversible and limited in blast radius.
From the tool's definition "Send a Wake-on-LAN magic packet to a MAC address"
Attacks that exploit this kind of access
The rule that runs wake_on_lan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wake_on_lan, this is the rule to start with:
wake_on_lan 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 Mcp Nettools, apply this rule, and every wake_on_lan call is checked against it from then on.
Questions about wake_on_lan
Send a Wake-on-LAN magic packet to a MAC address. It is categorised as a Execute tool in the Mcp Nettools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for wake_on_lan: 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 Mcp Nettools. Nothing to install.
wake_on_lan 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 wake_on_lan 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 wake_on_lan. 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.
wake_on_lan is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Nettools, and thousands of servers like it.
Across the catalogue