The monitor URLs (listenUrl and controlUrl) are indeed exposed to the client side. However, there are several security measures in place: - The listenUrl must use wss (secure WebSocket) protocol - The controlUrl must use https protocol - The assistant has controlEnabled set to true before allowing any control actions. Returns 400 error if control is disabled, and Validates the call is still active. While users could potentially access these URLs, the security impact is limited because: - The URLs are unique per call session - The control actions are restricted to non-destructive operations