The Agent dispatcher performs a JSON-based deep clone of constructor options before forwarding them to per-origin pools. Since JSON cannot represent functions, any `tls` option containing a `checkServerIdentity` callback is silently dropped. This allows a TLS peer to be accepted if it passes default hostname and chain checks, even if a custom `checkServerIdentity` was intended to reject it. This issue affects the default paths used by `request`, `fetch`, and `setGlobalDispatcher`, as well as the direct and no-proxy routes of `EnvHttpProxyAgent`. Only applications using function-valued `tls` options for tasks like certificate or public-key pinning are at risk.