DELETE /api/v2/vpn/ipsec/phase1
AI agents call pfsense_delete_vpn_ipsec_phase1 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.
This tool irreversibly removes IPSec VPN phase1 configurations from a pfSense firewall, permanently disabling VPN tunnels. This is a destructive operation with no automatic undo. The blast radius is critical because deleting VPN configurations can sever critical network connectivity, disrupt business operations, and potentially compromise security architecture.
From the tool's definition Tool name contains 'delete' and description shows DELETE HTTP method on VPN IPSec phase1 configuration endpoint. Deletes VPN tunnel configurations which cannot be undone without manual reconfiguration.
Attacks that exploit this kind of access
DELETE /api/v2/vpn/ipsec/phase1. 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.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_delete_vpn_ipsec_phase1: 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.
pfsense_delete_vpn_ipsec_phase1 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pfsense_delete_vpn_ipsec_phase1 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.
Set action: deny in the PolicyLayer policy for pfsense_delete_vpn_ipsec_phase1. 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.
pfsense_delete_vpn_ipsec_phase1 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.
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 →