Google Meet
ReviewAudited by ClawScan on May 1, 2026.
Overview
The skill coherently integrates with Google Meet through Maton OAuth, but it can access meeting data and perform meeting changes, so users should protect the Maton key and approve writes carefully.
Install this only if you trust Maton to broker Google Meet OAuth for your account. Keep MATON_API_KEY secret, specify the correct connection when you have multiple accounts, and require clear confirmation before any create, update, delete, or end-call action.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone with access to the Maton API key and connection could access the connected Google Meet account within the granted scope.
The skill uses Maton-managed OAuth to act on the user's connected Google Meet account, which is expected for the integration but is delegated account authority.
Maton proxies requests to `meet.googleapis.com` and automatically injects your OAuth token.
Use this only with a trusted Maton account, keep MATON_API_KEY private, choose the intended connection explicitly when needed, and revoke unused OAuth connections.
If a user approves the wrong action or target, the agent could create or change meeting spaces, end an active conference, or delete a connection.
The skill exposes meeting-changing API operations, including create, update, delete, and ending active calls; the artifact mitigates this by requiring explicit approval.
**All write operations require explicit user approval.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
Before approving any write action, verify the account, connection ID, meeting or space ID, and exact intended effect.
Meeting records, participant details, and related API responses may be processed by Maton as part of the managed OAuth flow.
Google Meet requests and responses are routed through the Maton gateway, so meeting metadata and participant information may transit a third-party service.
Base URL
```
https://api.maton.ai/google-meet/{native-api-path}
```
Maton proxies requests to `meet.googleapis.com`Confirm that using Maton as a proxy is acceptable for your organization and avoid requesting unnecessary sensitive meeting information.