pfsense_replace_services_cron_jobs

WHAT IT DOES

What pfsense_replace_services_cron_jobs does on Pfsense

AI agents invoke pfsense_replace_services_cron_jobs 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_replace_services_cron_jobs needs a policy

Replacing cron jobs on a firewall allows arbitrary scheduled command execution on the system. This is an Execute-class action with critical severity because an AI agent misusing this tool could schedule malicious commands to run on the firewall, compromising the entire network perimeter.

From the tool's definition PUT /api/v2/services/cron/jobs — replaces cron jobs on a pfSense firewall

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_replace_services_cron_jobs Rate-limited

pfsense_replace_services_cron_jobs 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_replace_services_cron_jobs": {
      "limits": [
        {
          "counter": "pfsense_replace_services_cron_jobs_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_replace_services_cron_jobs

What does the pfsense_replace_services_cron_jobs tool do? +

PUT /api/v2/services/cron/jobs. 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_replace_services_cron_jobs? +

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

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

Can I rate-limit pfsense_replace_services_cron_jobs? +

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

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

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