pfsense_create_firewall_schedule_time_range

WHAT IT DOES

What pfsense_create_firewall_schedule_time_range does on Pfsense

AI agents use pfsense_create_firewall_schedule_time_range to create or update resources in Pfsense — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pfsense environment.

WHY IT NEEDS A POLICY

Why pfsense_create_firewall_schedule_time_range needs a policy

This tool creates firewall schedule time ranges, which modifies firewall configuration in a reversible manner (schedules can be edited or deleted). While the description is empty, the name pattern matches other Write-category tools on this server (create_firewall_*). This is categorized as Write rather than Execute because it configures policy rather than directly executing network operations.

From the tool's definition Tool name contains 'create_firewall_schedule' which indicates creation of firewall scheduling rules. The server description states it gives 'full control over pfSense firewalls' and lists 'firewall schedule' among its capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_create_firewall_schedule_time_range Rate-limited

pfsense_create_firewall_schedule_time_range stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_firewall_schedule_time_range": {
      "limits": [
        {
          "counter": "pfsense_create_firewall_schedule_time_range_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_firewall_schedule_time_range

What does the pfsense_create_firewall_schedule_time_range tool do? +

pfsense_create_firewall_schedule_time_range. It is categorised as a Write tool in the Pfsense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pfsense_create_firewall_schedule_time_range? +

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

pfsense_create_firewall_schedule_time_range is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pfsense_create_firewall_schedule_time_range? +

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

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

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