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

pfsense_delete_services_bind_zones

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-services-bind-zones.md

What pfsense_delete_services_bind_zones does on Pfsense

AI agents call pfsense_delete_services_bind_zones 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_services_bind_zones is rated Critical

The 'delete' prefix indicates irreversible removal of DNS zone configurations from the BIND service. On a firewall system, deleting DNS zones cannot be easily undone and would disrupt DNS resolution for affected domains. This is destructive infrastructure manipulation that could significantly impact network operations.

From the tool's definition Tool name contains 'delete' verb applied to 'services_bind_zones' (DNS service configuration). The description is empty, but the naming pattern aligns with other sibling tools on this pfSense MCP server that perform irreversible modifications to critical…

Questions about pfsense_delete_services_bind_zones

What does the pfsense_delete_services_bind_zones tool do? +

pfsense_delete_services_bind_zones 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_services_bind_zones? +

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

pfsense_delete_services_bind_zones 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_services_bind_zones? +

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

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

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