Security audit
google-drive
Security checks for vulnerabilities and agentic risk
Overview
This is a disclosed Google Drive integration that uses Maton-managed authentication and requires user approval for writes, sharing, connections, and automation.
Use this only if you want Maton to access your Google Drive. Prefer OAuth, choose the narrowest Google scopes available, confirm every write/share/delete and every function or trigger destination, avoid exposing MATON_API_KEY, and periodically remove unused connections, triggers, and destinations.
Vulnerability Patterns
- Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
- Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
- Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
- Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
- Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
- Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
- Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
- Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
- Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
- Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Static analysis
No suspicious patterns detected.