pfsense_delete_vpn_openvpn_client_export_configs

pfsense_delete_vpn_openvpn_client_export_configs

Server Pfsense abl030/pfsense-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What pfsense_delete_vpn_openvpn_client_export_configs does on Pfsense

AI agents call pfsense_delete_vpn_openvpn_client_export_configs 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_openvpn_client_export_configs needs a policy

The 'delete' operation in the tool name indicates irreversible removal of VPN client export configurations. This is a destructive action that cannot be undone. While the description is empty, the context of a pfSense firewall management tool with 677 tools controlling critical infrastructure, combined with the explicit 'delete' action on VPN configurations, makes this a high-severity destructive operation.

From the tool's definition Tool name contains 'delete' and operates on VPN OpenVPN client export configs via pfSense REST API v2, which irreversibly removes configuration data.

Questions about pfsense_delete_vpn_openvpn_client_export_configs

What does the pfsense_delete_vpn_openvpn_client_export_configs tool do? +

pfsense_delete_vpn_openvpn_client_export_configs. 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_configs? +

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

pfsense_delete_vpn_openvpn_client_export_configs 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_configs? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.