Back to skill

Security audit

Oura

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed Oura connector for reading account wellness data, with sensitive data access that users should invoke deliberately.

Install only if you want agents to access your connected Oura account through OOMOL. Treat requests for sleep, readiness, heart rate, stress, activity, workouts, tags, device data, or personal information as sensitive, and avoid using the connector for general Oura questions that do not require your account data.

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
91% confidence
Finding
The skill description says to use this skill for "ANY Oura request" and "instead of calling the API directly," which creates an overly broad routing rule with no task or data-scope boundaries. In a health-data context, this can cause the agent to invoke a connector against a user's authenticated Oura account for loosely related requests, increasing the chance of unnecessary access to sensitive personal wellness data and reducing opportunities to apply narrower tool-selection or least-privilege logic.

Static analysis

No suspicious patterns detected.