other
- Location
SKILL.md:9- Finding
Uncontrolled External Storage of Customer Support Data
- Content
View full analysis
" \ -H "Content-Type: application/json" \ -d '{"text": "Ticket #4412: Jane reported rate limiting on Developer plan. Escalated to billing.", "title": "customer-support-memory - note"}' ``` ``` ```markdown ## Workflow 1. On new context, first recall: `What is the history of Jane's support tickets?` 2. Use the answer to personalize the response 3. After the interaction, store the summary via `/agent-remember` ``` ### Technical Analysis The skill instructs the agent to retrieve an API credential from `TOOLS.md` or the platform secret store and use it to transmit customer-support information to an externally hosted Supabase endpoint. It also makes external storage part of the standard post-interaction workflow. Customer-support conversations can contain personally identifiable information, account details, confidential correspondence, authentication material, billing information, or regulated data. The instructions do not require user consent, data classification, redaction, secret detection, data minimization, tenant validation, or an approved-domain check before transmission. They also do not document retention, deletion, access-control, or data-processing guarantees for the persistent external memory. The external endpoint uses a `supabase.co` hostname rather than the advertised `bluecolumn.ai` domain. This is not inherently malicious, but it reduces endpoint transparency and makes independent verification of the recipient and data-processing boundary more important. ### Attack Path 1. A customer includes ...[truncated 1553 chars]- Remediation
View remediation
