T09 · Insecure Skill Coding Practices
- Location
scripts/gmail_imap.py:112- Finding
Message sequence numbers are presented as UIDs, causing operations to target the wrong email
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The Gmail skill is mostly transparent about mailbox access, but a real identifier-handling flaw could move or trash the wrong email.
Review this skill before installing if you plan to let an agent move or trash email. Use a dedicated Google App Password, protect the environment variables, and avoid destructive commands until the script consistently uses stable IMAP UIDs and ideally confirms message metadata before moving or trashing mail.
scripts/gmail_imap.py:112Message sequence numbers are presented as UIDs, causing operations to target the wrong email
scripts/gmail_imap.py:238Email sending unnecessarily creates and leaves open an authenticated IMAP session
The skill documentation declares access to sensitive environment variables and inherently requires network connectivity to Gmail, but it does not define any explicit tool scope such as permissions or allowed-tools. That omission weakens policy enforcement and makes it easier for an agent runtime to grant broader-than-necessary capabilities, especially in a skill that can read, send, move, and delete email.
This markdown file instructs users to set GMAIL_IMAP_USER and GMAIL_IMAP_PASSWORD, which are sensitive credentials, but it does not include any warning about protecting those values or the privacy implications of granting mailbox access. Under the markdown-file criteria for missing user warnings, credential use affecting user privacy should be disclosed clearly.
No suspicious patterns detected.