AgentReadyHomeAgent Listing

← AgentDock

AgentDock — agentic threat model

8.5AIVSS 8.5 · High

AgentDock acts as a centralized hub and billing consolidator for multi-service AI agents, introducing a high-value target via its 'single API key' architecture. While its real-time cost monitoring and spending limits mitigate financial runaway risks, the concentration of API credentials presents a significant security aggregation risk.

OWASP AIVSS score rationale

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

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 — The framework orchestrates LLM calls but does not specify which foundation models are supported or how it protects against model-level threats like prompt injection or adversarial reprogramming.

L2 · Data Operations⚠ not certain from listing

Not certain from the listing — Mentions 'data enrichment' services, but details regarding data ingestion, vector database security, or RAG-specific poisoning protections are not provided.

L3 · Agent Frameworks✓ mapped

As an agent framework featuring a 'visual agent builder' and 'automatic failover', threats include insecure tool integration (e.g., voice, SMS, APIs) and logic flaws in the orchestration engine that could lead to unauthorized tool execution.

L4 · Deployment & Infrastructure⚠ not certain from listing

Not certain from the listing — While it is an open-source core (MIT license), the hosting environment, secrets management for the 'single API key', and execution sandboxing are not detailed.

L5 · Evaluation & Observability✓ mapped

Provides robust cost-focused observability ('monitor usage in real-time', 'spending limits'), but lacks explicit security-focused observability, such as anomaly detection for malicious prompt injections or payload tampering.

L6 · Security & Compliance (cross-cutting)✓ mapped

The 'single API key for all services' architecture simplifies billing but introduces a critical single point of failure. Compromise of this key or the AgentDock database grants access to all downstream services (SMS, voice, LLMs). No compliance certifications (e.g., SOC2) are mentioned.

L7 · Agent Ecosystem⚠ not certain from listing

Not certain from the listing — While it connects multiple external services (voice, SMS, APIs), it is unclear if it supports complex multi-agent collaboration or marketplace-based agent-to-agent trust boundaries.

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