An issue exists where the legacy `apiCall` service executor (pkg/engine/apicall/executor.go) and the `GlobalContextEntry` external-API path do not apply the default egress blocklist or scoped-token controls. These paths utilize a plain `net/http` client without egress filtering or validation of the configured service URL. Consequently, an author of a `ClusterPolicy` or `GlobalContextEntry`, or a lower-privileged resource submitter when a policy templates the service URL from the admission resource, can trigger GET/POST requests to arbitrary hosts. This includes cloud metadata endpoints, loopback addresses, and internal cluster services, potentially allowing the retrieval of cloud instance credentials. Additionally, the executor unconditionally attaches Kyverno's projected ServiceAccount token to the destination, although the token is audience-scoped.