pfsense_delete_vpn_wireguard_peer
A destructive tool on the Pfsense MCP server.
This record as markdown: /tools/abl030-pfsense-mcp/pfsense-delete-vpn-wireguard-peer.md
What pfsense_delete_vpn_wireguard_peer does on Pfsense
AI agents call pfsense_delete_vpn_wireguard_peer 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_vpn_wireguard_peer is rated Critical
The 'delete' prefix indicates irreversible removal of configuration. Deleting a WireGuard VPN peer removes network connectivity for that peer and cannot be undone without manual reconfiguration. On a production firewall controlling network access, this has severe blast radius. Classified as Destructive (not Execute) because deletion is inherently irreversible.
From the tool's definition Tool name contains 'delete' and 'vpn_wireguard_peer'; server description states tools cover 'VPN' and give 'full control over pfSense firewalls'; sibling tools include create/delete operations.
Attacks that exploit this kind of access
The rule that runs pfsense_delete_vpn_wireguard_peer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pfsense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pfsense_delete_vpn_wireguard_peer, this is the rule to start with:
pfsense_delete_vpn_wireguard_peer is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Pfsense, apply this rule, and every pfsense_delete_vpn_wireguard_peer call is checked against it from then on.
Questions about pfsense_delete_vpn_wireguard_peer
pfsense_delete_vpn_wireguard_peer 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.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_delete_vpn_wireguard_peer: 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_wireguard_peer 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_wireguard_peer 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_wireguard_peer. 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_wireguard_peer 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.
Across the catalogue