Uploading discloses the local file and its name to the connected Google Drive account
Source references: 6The command accepts any local file path and uploads it, retaining the source filename by default. The confirmation warning reduces accidental use, but the supplied source shows no content inspection, sensitive-data filtering, or destination-account verification.
If the user or agent selects the wrong file, Google account, or parent folder, the contents and potentially sensitive filename enter the wrong cloud location and become subject to that location's sharing, retention, and access rules.
The skill explicitly uploads a user-specified local file to Google Drive and uses the source filename by default, so execution transfers the file contents and filename into the currently authenticated Drive account. This matches the stated purpose and is not evidence of malicious behavior; the documentation also requires user confirmation. However, the shown instructions do not require checking the destination account or reviewing sensitive content. A user can require confirmation of the local path, account, parent folder, and remote filename, and authorize only specifically selected files.
```bashgws drive +upload <file>```Show 5 other places
|------|----------|---------|-------------|| `<file>` | ✓ | — | Path to file to upload || `--parent` | — | — | Parent folder ID || `--name` | — | — | Target filename (defaults to source filename) |- MIME type is detected automatically.- Filename is inferred from the local path unless --name is given.> [!CAUTION]> This is a **write** command — confirm with the user before executing.```bashgws drive +upload <file>```| Flag | Required | Default | Description ||------|----------|---------|-------------|| `<file>` | ✓ | — | Path to file to upload || `--parent` | — | — | Parent folder ID || `--name` | — | — | Target filename (defaults to source filename) |