Our understanding was that this permission was historically required for some of the on-page analysis provided by the plug-in. Following your comment, we have re-assessed the plugin's permission requirements and happy to say your concern will be addressed in an upcoming release.
