pfsense_create_services_wake_on_lan_send

WHAT IT DOES

What pfsense_create_services_wake_on_lan_send does on Pfsense

AI agents invoke pfsense_create_services_wake_on_lan_send to trigger actions in Pfsense. 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 IT NEEDS A POLICY

Why pfsense_create_services_wake_on_lan_send needs a policy

Wake-on-LAN sends a magic packet over the network to wake remote machines. This is an external operation that triggers real-world effects (powering on hardware). It is not merely writing data, but executing an action with network and physical side effects. Misuse could wake unauthorized devices or be used as part of a broader attack.

From the tool's definition POST /api/v2/services/wake_on_lan/send — 'send' indicates triggering an external network operation (Wake-on-LAN magic packet transmission) to remotely power on devices

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_create_services_wake_on_lan_send Rate-limited

pfsense_create_services_wake_on_lan_send 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": {
    "pfsense_create_services_wake_on_lan_send": {
      "limits": [
        {
          "counter": "pfsense_create_services_wake_on_lan_send_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pfsense, so you can run agents against it safely.

FAQ

Questions about pfsense_create_services_wake_on_lan_send

What does the pfsense_create_services_wake_on_lan_send tool do? +

POST /api/v2/services/wake_on_lan/send. It is categorised as a Execute tool in the Pfsense MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pfsense_create_services_wake_on_lan_send? +

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

What risk level is pfsense_create_services_wake_on_lan_send? +

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

Can I rate-limit pfsense_create_services_wake_on_lan_send? +

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

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

pfsense_create_services_wake_on_lan_send is provided by the Pfsense MCP server (abl030/pfsense-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.