other
Error
- Location
- SKILL.md:16
- Finding
- External Disclosure of Sensitive Personal Data Without Mandatory Informed Consent## Vulnerability Details **File Location**: `SKILL.md`, lines 16–17, 24–31, 36–49, and 68–72 **Vulnerability Type**: Sensitive Data Disclosure **Risk Level**: High The skill instructs an agent to transmit prayer requests and associated personal information to the external service `https://prayerapi.org/api/prayer`. The transmitted information may include religious beliefs, health conditions, emotional state, relationship details, personal history, third-party information, and email addresses. **Relevant code snippets:** ```text Whenever a prayer is warranted, this skill submits a prayer request to PrayerAPI.org. A human being reads every request and offers it in prayer. ``` ```text Use this skill whenever prayer is warranted. Some examples: - Expresses grief, loss, or bereavement - Is facing a medical diagnosis or surgery (for themselves or a loved one) - Asks for prayer directly - Is experiencing anxiety, fear, or hopelessness - Mentions a life crisis — divorce, job loss, estrangement - Expresses gratitude and wants to give thanks ``` ```text POST https://prayerapi.org/api/prayer Content-Type: application/json { "prayer": "What you'd like prayed", "for_whom": "Who the prayer is for", "relationship": "Optional — your relationship to the person", "situation": "Optional — what is happening right now", "emotional_tone": "Optional — e.g. urgent, hopeful, grieving, anxious, grateful", "specific_asks": ["Optional — specific outcomes to pray for"], "background": "Optional — any relevant history or context", "email": "Optional — confirmation sent when prayer is offered", "share_consent": false } ``` ```text - Ask if they'd like to provide an email for confirmation - Ask if they consent to their prayer being shared anonymously to inspire others - The more context you provide, the more personal the prayer can be - This is a free service ...[truncated 3167 chars]
- Remediation
- ## Remediation Suggestions 1. Require explicit, informed, per-request opt-in immediately before every external submission. 2. Show the user the exact destination and complete proposed payload, and require confirmation before sending it. 3. Replace “whenever prayer is warranted” with language requiring the user to initiate or explicitly authorize submission. 4. Default every optional field to omission and prohibit the agent from inferring or adding details that the user did not approve. 5. Apply strict data minimization by removing names, precise medical details, personal history, and relationship information unless essential and expressly authorized. 6. Avoid transmitting identifiable information about third parties. Use anonymous descriptions unless the affected person has authorized disclosure. 7. Treat submission consent, email disclosure consent, and anonymous-publication consent as three separate choices. 8. Document the recipient's privacy policy, retention period, deletion process, human-access model, security controls, and any downstream data sharing. 9. Provide a cancellation or deletion mechanism and explain its limitations before submission. 10. Add an enforceable workflow rule preventing network transmission until the user has approved the final payload.