Disconnect a specific VPN client
AI agents invoke openvpn_disconnect_client to trigger actions in OPNSense MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Disconnecting a VPN client is an operational action that terminates network connectivity for that client. It is not merely reading data, nor does it permanently delete/destroy data, but it does trigger an external operation (forcibly ending a session) with immediate real-world impact. Misuse could disrupt legitimate user access or network operations, warranting high severity.
From the tool's definition "Disconnect a specific VPN client" — actively terminates an existing VPN connection
Documented attack patterns abuse exactly the kind of access openvpn_disconnect_client gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OPNSense MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for openvpn_disconnect_client:
{
"version": "1",
"default": "deny",
"tools": {
"openvpn_disconnect_client": {
"limits": [
{
"counter": "openvpn_disconnect_client_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}openvpn_disconnect_client stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Disconnect a specific VPN client. It is categorised as a Execute tool in the OPNSense MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for openvpn_disconnect_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 OPNSense MCP Server. Nothing to install.
openvpn_disconnect_client is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the openvpn_disconnect_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 openvpn_disconnect_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.
openvpn_disconnect_client is provided by the OPNSense MCP Server MCP server (vespo92/opnsensemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 196 OPNSense MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
196 OPNSense MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.