mcp-google-workspace: why it is not safe to use

What we found

Our review did not find hidden prompts, hardcoded secrets, obfuscated code, undisclosed remote fetches, or access to unrelated credential stores. Network use appeared limited to Google OAuth and Google Workspace APIs that the user chooses to authorize.

The main concern is operational safety. This skill can take irreversible or hard-to-undo actions in Gmail and Google Calendar when the relevant permissions are enabled. Based on the repo, those actions can include deleting calendar events and Gmail drafts, archiving messages, and sending replies. We did not see an in-skill confirmation step before those actions occur. That means a mistaken instruction, overly broad prompt, or automation error could cause changes in a live mailbox or calendar without a final check inside the skill.

What to do instead

Use this skill only with the minimum Google scopes needed, and prefer read-only access where possible. If write access is required, use it in workflows that add an explicit human approval step before delete, archive, or send actions. For higher-risk environments, test against a secondary Google account or non-production calendar first, and limit which accounts and data the skill can access.