Security audit
Security checks for vulnerabilities and agentic risk
This is a straightforward Google Calendar gateway guide, but it enables reading, changing, deleting, and notifying people from the user's primary calendar without clear confirmation guidance.
Review this skill before installing if you use Google Calendar for sensitive personal or business scheduling. Only use it with a Maton API key you trust, confirm event IDs before updates or deletion, and explicitly approve attendee email addresses and whether notifications should be sent.
The document emphasizes Australia/Melbourne and uses that time zone throughout the examples, which can function as a locale constraint. Because no opt-in or justification is provided, this appears to force a specific locale contrary to the natural-language policy requirement.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl "https://gateway.maton.ai/google-calendar/calendar/v3/calendars/primary/events?maxResults=20&singleEvents=true&orderBy=startTime" \
-H "Authorization: Bearer $MATON_API_KEY"
The example sends invitations/updates to attendees using sendUpdates="all" without warning that this triggers outbound communications to external recipients. An agent following this skill could contact unintended parties, leak meeting metadata, or create unauthorized invitations without clear user consent.
Updating attendees with sendUpdates="all" can immediately notify recipients, but the skill provides no caution about external communications or consent requirements. This can cause privacy issues, unintended outreach, and unauthorized calendar changes visible to third parties.
The skill documents a destructive delete operation with no caution, confirmation requirement, or note that deletion can permanently remove calendar events. In an agent context, this increases the risk of accidental or unauthorized destructive actions being performed on a user's primary calendar.
No suspicious patterns detected.