Security Considerations When Reading SQL Errors Logs Via PowerShell

Hello,

I recently learned that I can use PS to parse SQL Error Logs, which is something I am currently doing manually.  As such, I would like to set up a SQL job that runs a PS script that queries the Error logs and sends out and email if it encounters any unusual log entries.  However, to get this to work the account that the PS script runs under needs to be a member of the SecurityAdmin SQL Server role.  It seems a bit excessive to give this account the SecurityAdmin role when all it is doing is reading the error log.  

Does anyone have suggestions on how I can get around this (ie how can I use PowerShell to parse the SQL Error log without using an account that has the SecurityAdmin role)?

Thanks