It's better to stay away from database owner chaining.

In your situation, you can grant permissions on underlying objects in other database to users executing the procedure, or you can sign your procedure with a certificate to avoid allowing users to access underlying objects.

If you want to learn more about procedure signing, this should help: https://www.sqlskills.com/blogs/jonathan/certificate-signing-stored-procedures-in-multiple-databases/