Reclaim AI — agentic threat model
Reclaim AI presents a moderate-high risk profile primarily due to its write-access integration with Google Calendar via OAuth, which could be leveraged for data exfiltration, meeting hijacking, or social engineering if compromised.
OWASP AIVSS score rationale
| Autonomy of Action | 0.70 | |
| Goal-Driven Planning | 0.60 | |
| Self-Modification | 0.10 | |
| Dynamic Tool Use | 0.60 | |
| Persistent Memory | 0.70 | |
| Contextual Awareness | 0.80 | |
| Dynamic Identity | 0.40 | |
| Multi-Agent Interactions | 0.20 | |
| Non-Determinism | 0.40 | |
| Opacity & Reflexivity | 0.30 |
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.
Not certain from the listing — The specific foundation models or heuristic algorithms used for scheduling are not disclosed. Potential threats include adversarial manipulation of task inputs to disrupt scheduling logic.
Not certain from the listing — The system ingests highly sensitive calendar metadata, task descriptions, and user habits, but details on data storage, encryption, or vector databases are omitted. Threats include unauthorized access to historical and future schedule data.
Not certain from the listing — The orchestration framework is proprietary. The agent uses tools to read/write to Google Calendar. Threats include insecure tool integration and API token leakage, allowing unauthorized calendar modifications.
Not certain from the listing — The hosting infrastructure and sandboxing mechanisms for this closed-source SaaS are not described. Threats include container compromise or database breaches exposing OAuth credentials.
Not certain from the listing — No details are provided regarding logging, drift detection, or guardrails. Gaps here could allow silent scheduling manipulation or unauthorized calendar modifications to go unnoticed.
Not certain from the listing — While Google OAuth verification is implied, specific compliance certifications (e.g., SOC2, ISO 27001) or data retention policies are not detailed in the listing.
Not certain from the listing — The agent coordinates schedules across teams, but there is no evidence of an autonomous multi-agent ecosystem or marketplace interaction that could lead to cascading agent-to-agent trust failures.
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.