vpn_client
Configure outbound VPN profiles, select the active one, and add or remove devices so chosen clients route through a filtering VPN.
Instructions
The router's VPN CLIENT (router dials out). Configure a VPN, then choose which devices use it - this is how e.g. a child's device can be sent through a filtering VPN. Profiles: action=profiles | add_profile (profile={key,...}; added disabled) | set_active_profile (key; the ENABLED profile is the one in use) | update_profile / remove_profile (key). Devices (they use WHICHEVER profile is active; there is no per-device profile): devices | candidates | add_device (mac, name?, client_type?) | set_device (mac, use_vpn=true|false) | remove_device (mac). Also status | connection_status (key) | enable | disable. Everything that changes profiles or devices is CRITICAL.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "vpn_client"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | ||
| mac | No | ||
| name | No | ||
| apply | No | false (default) = dry run: show the plan, diff, warnings and risk, send nothing. true = send it. | |
| action | No | status | |
| reveal | No | Show secrets (passwords/keys) unmasked. | |
| router | No | Which router (see router_status 'routers'); default main. | main |
| profile | No | ||
| use_vpn | No | ||
| client_type | No | ||
| confirm_token | No | Required with apply=true for CRITICAL changes: the token from the dry run (valid 5 minutes, bound to the exact plan and current router state). |