T08 · Insecure Dependencies
- Location
SKILL.md:45- Finding
Unpinned External Dependencies Permit Mutable Code Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill exposes Google Workspace through the official-style gws CLI and MCP, with broad account powers that are visible and purpose-aligned but require careful scope control.
Install only if you intend to let an agent work with your Google Workspace account. Prefer pinned or reviewed CLI versions, avoid all-services MCP mode, grant the smallest OAuth scopes possible, restrict MCP to needed services, and require explicit confirmation before sending email, sharing files, deleting or modifying data, or using Admin APIs.
SKILL.md:45Unpinned External Dependencies Permit Mutable Code Installation
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
2. Enable Workspace APIs (Drive, Gmail, Calendar, etc.)
3. Create OAuth 2.0 Client ID (Desktop app type)
4. Download credentials JSON
5. Set: `export GOOGLE_WORKSPACE_CLI_CREDENTIALS_FILE=/path/to/credentials.json`
6. Run: `gws auth login`
### Option C: Service Account (server/headless)
The skill explicitly advertises capabilities to read/send Gmail, modify calendars and sheets, and manage Drive, but it does not clearly warn users that these actions can modify data, share content, or send outbound communications on their behalf. In an agent context, this increases the risk of unintended side effects, especially when the tool is exposed through MCP and can be invoked programmatically across many Workspace APIs.
No suspicious patterns detected.