If you change the license, they will capture your tool and use it against the hacking community without any risk.
They won't try to impose a closed source alternative because they care for their #OSS narrative.
They will try to build a MIT alternative from scratch under their full control.
BUT by doing so, they might have legal issues with #antitrust as, given the existance of a copyleft alternative, their replacement will makes it clear that #Google is trying to build yet another #monopoly.
Instead if you surrender to their pressure and weaken the license of your tool, you make their OSS-based propaganda stronger and harder the antitrust case against them, because they will argue "hey, we just contributed to the ecosystem", while they got control of it.
So my suggestion in your case is to stick to the #AGPLv3.
Don't trust neither Google nor Google's engineers.
I did this error before, and it didn't end well:
http://www.tesio.it/2018/02/14/what-i-wish-i-knew-before-contributing-to-open-source.html
