AI agents use pfsense_create_vpn_openvpn_client to create or update resources in Pfsense — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pfsense environment.
This tool creates OpenVPN client configurations on pfSense firewalls, which is a reversible modification (Write category). However, it affects critical network security infrastructure (VPN access), warranting high severity due to potential for unauthorized VPN connections, network exposure, or security bypass if misused by an AI agent. The context of full firewall control via REST API elevates the risk profile.
From the tool's definition Tool name contains 'create' and targets 'vpn_openvpn_client', indicating creation/modification of VPN client configuration. Description is empty, limiting specificity.
Attacks that exploit this kind of access
pfsense_create_vpn_openvpn_client. It is categorised as a Write tool in the Pfsense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_create_vpn_openvpn_client: 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_create_vpn_openvpn_client is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pfsense_create_vpn_openvpn_client 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_create_vpn_openvpn_client. 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_create_vpn_openvpn_client 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 →