Security audit
Security checks for vulnerabilities and agentic risk
This skill documents an agent email service with clearly disclosed mailbox access, account controls, credential storage, and usage costs.
Mailgi will host your messages, and its API key permits mailbox changes and sending. Protect saved keys and keep recipients and permanent deletion under your control. Review external-send and storage costs, including shared organization funds, and separately review optional package installs or refreshed instructions.
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
Delete a folder:
DELETE /v1/mailboxes/<id>
Authorization: Bearer <apiKey>
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
Delete a message (moves to Trash):
DELETE /v1/mail/<id>
Authorization: Bearer <apiKey>
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
Response includes `apiKey` (raw, shown once) and `id`.
List keys: `GET /v1/apikeys`
Revoke a key: `DELETE /v1/apikeys/<keyId>`
---
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
Manage them:
GET /v1/webhook-endpoints — list yours, as { endpoints: [...] }
DELETE /v1/webhook-endpoints/<id> — remove one
GET /v1/webhook-endpoints/<id>/deliveries — recent delivery attempts
POST /v1/webhook-endpoints/<id>/deliveries/<deliveryId>/resend
POST /v1/webhook-endpoints/<id>/enable — see "disabled" below
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
DELETE /v1/agents/me
Authorization: Bearer <apiKey>
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
"receivedAt": "2026-09-03T10:00:00Z", "size": 4096, "spam": false, "fetchUrl": "https://api.mailgi.xyz/v1/mail/" }
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# 1. Register
RESP=$(curl -s -X POST https://api.mailgi.xyz/v1/agents/register \
-H "Content-Type: application/json" \
-d '{"label":"my-agent"}')
EMAIL=$(echo $RESP | jq -r .emailAddress)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# 1. Register
RESP=$(curl -s -X POST https://api.mailgi.xyz/v1/agents/register \
-H "Content-Type: application/json" \
-d '{"label":"my-agent"}')
EMAIL=$(echo $RESP | jq -r .emailAddress)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# 402 with a top-up link (see §4). Give the mailbox a moment first: sending
# right after registering can 500 while it is provisioned. Retry once if so.
sleep 3
curl -s -X POST https://api.mailgi.xyz/v1/mail/send \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d "{\"to\":[\"$EMAIL\"],\"subject\":\"Hi\",\"textBody\":\"Hello from $EMAIL\"}"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
-d "{"to":["$EMAIL"],"subject":"Hi","textBody":"Hello from $EMAIL"}"
curl -s https://api.mailgi.xyz/v1/mail
-H "Authorization: Bearer $KEY"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
---
Full interactive docs: https://api.mailgi.xyz/docs
Machine-readable spec: https://api.mailgi.xyz/openapi.json
---
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
---
Full interactive docs: https://api.mailgi.xyz/docs
Machine-readable spec: https://api.mailgi.xyz/openapi.json
---
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# 402 with a top-up link (see §4). Give the mailbox a moment first: sending
# right after registering can 500 while it is provisioned. Retry once if so.
sleep 3
curl -s -X POST https://api.mailgi.xyz/v1/mail/send \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d "{\"to\":[\"$EMAIL\"],\"subject\":\"Hi\",\"textBody\":\"Hello from $EMAIL\"}"
No suspicious patterns detected.