Back to skill

Security audit

AWS S3

Security checks for vulnerabilities and agentic risk

Overview

This S3 connector skill is mostly coherent, but one sensitive URL-generation action is under-scoped compared with its own safety rules.

Review this skill before installing if your S3 buckets contain sensitive or business-critical data. Only allow presigned URL generation when the object, permission type, recipient, and expiration are clear, and approve setup commands such as installing the oo CLI only if you trust OOMOL as the connector provider.

Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
Findings (1)

Vague Triggers

Medium
Confidence
97% confidence
Finding
The trigger/description is extremely broad: it instructs the agent to use this skill for ANY AWS S3 request and effectively for any task involving S3 instead of direct API use. In an agentic environment, this can cause over-invocation on ambiguous mentions of S3 and route read, write, or destructive operations through the skill without sufficient task-specific narrowing, increasing the chance of unintended data access or modification.

Static analysis

No suspicious patterns detected.