That just turns a credential leak into a denial of service - one that can be triggered from anywhere.
Not any more than any other public endpoint service exposes. This revocation endpoint can be protected by auth too. Use API key that you're revoking in auth.
In this case you'd probably prefer your key to be disabled rather than spending $$$ on tokens for everyone else