AgentReadyHomeAgent Listing

← eye type detector

eye type detector — agentic threat model

4.7AIVSS 4.7 · Medium

The eye type detector is a low-risk, single-purpose utility with minimal agentic capabilities, presenting primary risks around the privacy and handling of user-uploaded facial images.

OWASP AIVSS score rationale

AIVSS = (CVSS_Base + AARS) × Mitigation_Factor, where AARS = (10 − CVSS_Base) × (Factor_Sum / 10) × ThM
CVSS base 4.3AARS uplift 0.43Factor sum 0.8/10Threat ×0.95Mitigation ×1.0
Autonomy of Action
0.10
Goal-Driven Planning
0.00
Self-Modification
0.00
Dynamic Tool Use
0.10
Persistent Memory
0.00
Contextual Awareness
0.10
Dynamic Identity
0.00
Multi-Agent Interactions
0.00
Non-Determinism
0.30
Opacity & Reflexivity
0.20

Scored with the canonical OWASP AIVSS formula (AIVSS calculator reference); agentic risk factors estimated from the agent’s described capabilities.

MAESTRO 7-layer threat model

Per-layer threats for this agent. Layers tagged “not certain from listing” are general, caveated commentary where the public description didn’t pin that layer.

L1 · Foundation Models✓ mapped

Uses vision-based models to analyze eye shape. Vulnerable to adversarial image perturbations that spoof classification results, and potential model extraction attacks.

L2 · Data Operations✓ mapped

Processes user-uploaded facial images. Risks include unauthorized data retention, lack of encryption in transit/at rest, and potential exfiltration of biometric-adjacent data.

L3 · Agent Frameworks⚠ not certain from listing

Not certain from the listing — framework details are not provided, but likely a simple single-turn inference pipeline with minimal agentic orchestration or tool calling.

L4 · Deployment & Infrastructure⚠ not certain from listing

Not certain from the listing — infrastructure details are undisclosed, but standard web hosting risks apply to the image upload and processing endpoints, including potential denial of service via large image payloads.

L5 · Evaluation & Observability⚠ not certain from listing

Not certain from the listing — no observability or guardrail mechanisms are mentioned for detecting adversarial inputs, malicious file uploads, or monitoring classification drift.

L6 · Security & Compliance (cross-cutting)⚠ not certain from listing

Not certain from the listing — compliance posture regarding biometric data processing, user consent, and data deletion policies (e.g., GDPR/CCPA) is unstated.

L7 · Agent Ecosystem✓ mapped

Operates as a standalone single-purpose utility with no multi-agent coordination or ecosystem integrations described.

MAESTRO — the 7-layer agentic threat-modeling framework (Cloud Security Alliance / Ken Huang).