pfsense_delete_status_openvpn_server_connection

WHAT IT DOES

What pfsense_delete_status_openvpn_server_connection does on Pfsense

AI agents call pfsense_delete_status_openvpn_server_connection 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 IT NEEDS A POLICY

Why pfsense_delete_status_openvpn_server_connection needs a policy

This tool performs an irreversible action that terminates an OpenVPN server connection. While not data deletion in the traditional sense, it forcibly disconnects active VPN sessions which cannot be undone and disrupts established network connectivity.

From the tool's definition Tool name contains 'delete' and description shows DELETE HTTP method on a status endpoint for OpenVPN server connections. This operation irreversibly terminates an active VPN connection.

Attacks that exploit this kind of access

Questions about pfsense_delete_status_openvpn_server_connection

What does the pfsense_delete_status_openvpn_server_connection tool do? +

DELETE /api/v2/status/openvpn/server/connection. 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_status_openvpn_server_connection? +

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

pfsense_delete_status_openvpn_server_connection 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_status_openvpn_server_connection? +

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

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

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