Security audit
Security checks for vulnerabilities and agentic risk
This skill needs review because it enables changes and deletions to sensitive family records without requiring approval for each action.
Install only if you intend to grant an agent direct OFW write access. Require your approval before sending, deleting, changing expenses or visibility, uploading shared files, or creating journal entries. For retrieval alone, prefer an integration with enforced read-only limits. Reading an unread message can mark it read, and browser pairing remains until revoked.
The service, resource, and curl implementation align with the description, but deleting messages materially exceeds the stated purpose of accessing OFW data. This is an undeclared destructive capability, not merely a supporting implementation detail.
The GET request matches the declared expense-access purpose. The PUT request introduces an undeclared state-changing capability, explicitly setting isPrivate to false. Changing record visibility is materially different from retrieving OFW data, not merely a supporting implementation detail. The supplied body contains a placeholder, so the chunk does not establish that the update would execute successfully as written.
The endpoint and authentication mechanism align with the declared OFW integration, but deleting calendar events goes beyond the described data-access purpose. The description does not disclose destructive calendar operations.
The declared purpose emphasizes accessing OFW data, but the supplied command performs a state-changing file upload. Although it uses the expected OFW domain and authentication mechanism, transmitting local file contents and creating an uploaded file are additional capabilities not disclosed in the description. The command does not itself send a message.
The code uses the declared OFW API and authentication mechanism, but performs an externally visible write: POSTing a message with draft set to false. The description emphasizes accessing OFW data and does not disclose sending messages or otherwise modifying account state. The subsequent GET is supporting verification, not a separate mismatch.
The service and direct REST access match the description, but the description frames the skill as accessing OFW data without declaring write operations. This code changes server-side calendar data rather than merely retrieving it, introducing an undeclared modification capability.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
attachments:{myFileIDs:$myFileIDs}, draft:($draft=="true"),
includeOriginal:($includeOriginal=="true"), replyToId:$replyToId}')
RESP=$(curl -s -X POST 'https://ofw.ourfamilywizard.com/pub/v3/messages' \
"${AUTH_HEADERS[@]}" -H 'Content-Type: application/json' --data "$BODY")
NEW_ID=$(jq -r '.id // .entityId // empty' <<<"$RESP")
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
eventFor: "neither",
children: [67890]
}')
curl -s -X POST 'https://ofw.ourfamilywizard.com/pub/v1/calendar/events'
"${AUTH_HEADERS[@]}" -H 'Content-Type: application/json' --data "$BODY" | jq .
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Update an event (send only the fields you're changing):
curl -s -X PUT "https://ofw.ourfamilywizard.com/pub/v1/calendar/events/${EVENT_ID}" \
"${AUTH_HEADERS[@]}" -H 'Content-Type: application/json' \
--data '{"title":"Soccer practice (moved)","startDate":"2026-07-20T17:00:00"}' | jq .
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
single receipt file are optional.
curl -s -X POST 'https://ofw.ourfamilywizard.com/pub/v2/expense' \
"${AUTH_HEADERS[@]}" -H 'Content-Type: application/json' \
--data '{
"title":"Soccer cleats",
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s "https://ofw.ourfamilywizard.com/pub/v2/expense/expenses/${EXPENSE_ID}" "${AUTH_HEADERS[@]}" | jq .
curl -s -X PUT "https://ofw.ourfamilywizard.com/pub/v2/expense/expenses/${EXPENSE_ID}" \
"${AUTH_HEADERS[@]}" -H 'Content-Type: application/json' \
--data '{ …every current field…, "isPrivate":false }' | jq .
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Create an entry (write — journal entries are a permanent court record):
curl -s -X POST 'https://ofw.ourfamilywizard.com/pub/v1/journals' \
"${AUTH_HEADERS[@]}" -H 'Content-Type: application/json' \
--data '{"title": "Missed pickup", "body": "Co-parent arrived 45 min late without notice."}' | jq .
No suspicious patterns detected.