An application which does "no IO" does nothing other than make the computer get hot. Why even run it?
Why, for testing. The calls to IO are replaced with calls to mocks which are then used to verify IO behavior. It's like replacing the IO monad with a type that doesn't actually do IO, only it doesn't require the code to change, so it works even for third-party code.
You can then use the security manager during the test to verify that all IO calls are indeed mocked.
True, the security manager does not limit access to the random-number generator, but this, too, can be done with an extra bit of one-time effort, by injecting a security check into the random number generator's seed generation method (we still want to allow fixed seeds like StdGen).
[1]: Or a finer-grained policy of "no IO except for logging".