pfsense_post_diagnostics_command_prompt

WHAT IT DOES

What pfsense_post_diagnostics_command_prompt does on Pfsense

AI agents invoke pfsense_post_diagnostics_command_prompt 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_command_prompt needs a policy

This tool executes arbitrary commands on a network firewall appliance. Misuse could allow full system compromise, network reconfiguration, data exfiltration, or complete firewall bypass. The blast radius is critical as it provides root-level access to a security-critical network infrastructure device.

From the tool's definition POST /api/v2/diagnostics/command_prompt — 'command_prompt' indicates arbitrary shell command execution on the pfSense firewall

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_post_diagnostics_command_prompt Rate-limited

pfsense_post_diagnostics_command_prompt 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_command_prompt": {
      "limits": [
        {
          "counter": "pfsense_post_diagnostics_command_prompt_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_command_prompt

What does the pfsense_post_diagnostics_command_prompt tool do? +

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

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

pfsense_post_diagnostics_command_prompt 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_command_prompt? +

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

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

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