Unexpected external access to Karate mock endpoints during test execution

Symptom

When executing Karate tests that utilize the built‑in mock server, there is uncertainty about whether the mock endpoints are bound only to the intended interface (e.g., localhost) or could become reachable from external networks.

The goal is to confirm that the mock service remains isolated to the test environment and to identify any configuration options that control its network exposure.

What steps can be taken to verify the binding address of Karate mock endpoints? Are there specific Karate configuration properties that restrict the mock server to localhost or a private subnet? Are there known scenarios where accidental public exposure might occur despite default settings?