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

pfsense_delete_routing_gateway

DELETE /api/v2/routing/gateway

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-routing-gateway.md

What pfsense_delete_routing_gateway does on Pfsense

AI agents call pfsense_delete_routing_gateway 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_routing_gateway is rated Critical

Deleting a routing gateway is an irreversible action that cannot be undone and would immediately break network routing functionality on the pfSense firewall. This could cause complete loss of network connectivity or isolation of critical segments.

From the tool's definition Tool performs DELETE operation on routing gateway configuration via REST API. The name explicitly contains 'delete' and the HTTP method is DELETE, indicating irreversible removal of firewall routing infrastructure.

Questions about pfsense_delete_routing_gateway

What does the pfsense_delete_routing_gateway tool do? +

DELETE /api/v2/routing/gateway. 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_routing_gateway? +

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

pfsense_delete_routing_gateway 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_routing_gateway? +

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

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

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