New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

pfsense_delete_firewall_schedule_time_range

A destructive tool on the Pfsense MCP server.

SERVERPfsense SOURCEabl030/pfsense-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/abl030-pfsense-mcp/pfsense-delete-firewall-schedule-time-range.md

What pfsense_delete_firewall_schedule_time_range does on Pfsense

AI agents call pfsense_delete_firewall_schedule_time_range to permanently remove resources in Pfsense, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why pfsense_delete_firewall_schedule_time_range is rated Critical

The delete operation irreversibly removes firewall schedule time range configurations. While the description is empty, the explicit 'delete' action in the name combined with the firewall management context indicates this is a destructive operation. Deleting firewall schedule configurations could disrupt network access controls and cannot be undone without manual reconfiguration.

From the tool's definition Tool name contains 'delete' and operates on firewall schedule time ranges. The server description indicates 'full control over pfSense firewalls' with tools covering 'firewall rules, NAT, VPN, services, routing' and more.

Questions about pfsense_delete_firewall_schedule_time_range

What does the pfsense_delete_firewall_schedule_time_range tool do? +

pfsense_delete_firewall_schedule_time_range is a destructive tool on the Pfsense MCP server. It is categorised as a Destructive tool in the Pfsense MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on pfsense_delete_firewall_schedule_time_range? +

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

pfsense_delete_firewall_schedule_time_range is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pfsense_delete_firewall_schedule_time_range? +

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

Set action: deny in the PolicyLayer policy for pfsense_delete_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_delete_firewall_schedule_time_range? +

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

More on Pfsense, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Pfsense's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.