pfsense_post_diagnostics_reboot · Pfsense MCP: Risk & Policy

WHAT IT DOES

What pfsense_post_diagnostics_reboot does on Pfsense

AI agents invoke pfsense_post_diagnostics_reboot 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_post_diagnostics_reboot needs a policy

Rebooting a firewall is an external operation with significant blast radius: it drops all active connections, disrupts network traffic, and causes downtime for all systems behind the firewall. It is an Execute action (triggering an external system operation), not Destructive (no data is permanently deleted), but the severity is critical due to the potential for complete network outage.

From the tool's definition POST /api/v2/diagnostics/reboot — triggers a system reboot of the pfSense firewall

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_post_diagnostics_reboot Rate-limited

pfsense_post_diagnostics_reboot 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_post_diagnostics_reboot": {
      "limits": [
        {
          "counter": "pfsense_post_diagnostics_reboot_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_post_diagnostics_reboot

What does the pfsense_post_diagnostics_reboot tool do? +

POST /api/v2/diagnostics/reboot. 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_post_diagnostics_reboot? +

Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_post_diagnostics_reboot: 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_post_diagnostics_reboot? +

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

Can I rate-limit pfsense_post_diagnostics_reboot? +

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

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

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