AgentReadyHomeAgent ListingPricing

← Joy

Joy — agentic threat model

6.0AIVSS 6.0 · Medium

Joy presents a moderate risk profile as a hybrid AI-human answering service; while its direct autonomy is mitigated by live agent integration, it handles sensitive customer PII and integrations with business scheduling/CRM tools.

OWASP AIVSS score rationale

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

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⚠ not certain from listing

Not certain from the listing — likely relies on commercial or proprietary LLMs optimized for dialogue. Main threats include prompt injection leading to social engineering of callers or unauthorized disclosure of system instructions.

L2 · Data Operations⚠ not certain from listing

Not certain from the listing — processes real-time caller transcripts, customer PII, and business-specific FAQs. Main threats include data exfiltration of sensitive caller history and poisoning of the business knowledge base.

L3 · Agent Frameworks⚠ not certain from listing

Not certain from the listing — orchestrates dialogue state and manages the transition between AI and live agents. Main threats include state-manipulation attacks that bypass live-agent routing or hijack tool execution (e.g., booking systems).

L4 · Deployment & Infrastructure⚠ not certain from listing

Not certain from the listing — likely deployed on cloud infrastructure integrated with telephony (VoIP/SIP) or web chat widgets. Main threats include insecure API endpoints, session hijacking, and telephony-specific denial of service.

L5 · Evaluation & Observability⚠ not certain from listing

Not certain from the listing — requires robust monitoring of call quality, transcription accuracy, and handoff triggers. Main threats include blind spots in detecting prompt injection via voice (indirect injection) and lack of real-time anomaly detection.

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

Not certain from the listing — must adhere to privacy regulations (GDPR, CCPA) and potentially HIPAA/PCI-DSS depending on the business vertical. Main threats include inadequate access controls to call recordings and lack of end-to-end encryption for voice data.

L7 · Agent Ecosystem⚠ not certain from listing

Not certain from the listing — operates in a hybrid ecosystem interacting directly with live human agents and external CRM/scheduling APIs. Main threats include the AI being manipulated to social-engineer the live agents or triggering cascading sync failures in downstream CRMs.

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

These scores are auto-generated from public information (the agent's own listing, docs, and repository) using the canonical OWASP AIVSS formula and the MAESTRO framework — an estimate for guidance, not a penetration test, audit, or certification. See the scoring methodology. Are you the vendor? Factual corrections are free.