pfsense_delete_network_interfaces

pfsense_delete_network_interfaces

Server Pfsense abl030/pfsense-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What pfsense_delete_network_interfaces does on Pfsense

AI agents call pfsense_delete_network_interfaces 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_network_interfaces needs a policy

Network interface deletion is a destructive operation that permanently removes configuration and cannot be easily restored without manual intervention or backup restoration. Given the tool's name explicitly contains 'delete' and operates on critical firewall infrastructure, it represents an irreversible action with severe consequences (network outage, firewall unavailability).

From the tool's definition Tool name 'pfsense_delete_network_interfaces' contains 'delete' which indicates irreversible removal of network interface configuration. The server context indicates this tool operates on pfSense firewall infrastructure via REST API v2.

Questions about pfsense_delete_network_interfaces

What does the pfsense_delete_network_interfaces tool do? +

pfsense_delete_network_interfaces. 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_network_interfaces? +

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

pfsense_delete_network_interfaces 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_network_interfaces? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.