pfsense_replace_services_cron_jobs
PUT /api/v2/services/cron/jobs
This record as markdown: /tools/abl030-pfsense-mcp/pfsense-replace-services-cron-jobs.md
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 pfsense_replace_services_cron_jobs is rated High
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
The rule that runs pfsense_replace_services_cron_jobs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pfsense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pfsense_replace_services_cron_jobs, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Pfsense, apply this rule, and every pfsense_replace_services_cron_jobs call is checked against it from then on.
Questions about pfsense_replace_services_cron_jobs
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.
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.
pfsense_replace_services_cron_jobs 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 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.
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.
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.
More on Pfsense, and thousands of servers like it.
Across the catalogue