pfsense_delete_vpn_openvpn_client_export_config

WHAT IT DOES

What pfsense_delete_vpn_openvpn_client_export_config does on Pfsense

AI agents call pfsense_delete_vpn_openvpn_client_export_config 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_vpn_openvpn_client_export_config needs a policy

This tool performs an irreversible deletion of OpenVPN client export configuration. Once deleted, the configuration cannot be recovered without manual recreation. While not directly affecting firewall rules or system access, losing VPN client configurations could disrupt VPN connectivity and require manual reconfiguration.

From the tool's definition Tool name contains 'delete' and description shows DELETE HTTP method targeting VPN OpenVPN client export configuration via REST API. The action irreversibly removes VPN client configuration data.

Attacks that exploit this kind of access

Questions about pfsense_delete_vpn_openvpn_client_export_config

What does the pfsense_delete_vpn_openvpn_client_export_config tool do? +

DELETE /api/v2/vpn/openvpn/client_export/config. 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_vpn_openvpn_client_export_config? +

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

pfsense_delete_vpn_openvpn_client_export_config 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_vpn_openvpn_client_export_config? +

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

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

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