send-email — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited send-email (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use the mailbridge MCP tools to compose and send emails.
Call send_email with:
to — recipient addresssubject — subject linebody — plain text bodycc / bcc — optionalrequest_receipt — set true if the user wants to know when the email is opened (see Read Receipts below)attachments — optional array to send files (see Attachments below)Always confirm before sending. Show the draft first:
To: [email protected]
Subject: Your subject
---
Body of the email...
---
Send this? (yes / edit / save as draft)send_emailsave_draftschedule_emailIf the user wants to reply to an existing message, use reply_to_email with:
uid — UID of the original emailbody — reply textfolder — folder containing the original (default: INBOX)The tool automatically sets Re: prefix and threading headers.
Same confirmation step applies before sending.
reply_to_email also accepts request_receipt and attachments — same behaviour as send_email.
Both send_email and reply_to_email accept an optional attachments array. Each item is one of:
{ "path": "/path/to/file.pdf" } — a file on the local filesystem (filename is inferred; pass filename to override){ "filename": "report.csv", "content_base64": "..." } — inline content you already have, base64-encodedEach file must be ≤ 20 MB. If a path doesn't exist or a file is too large, the tool returns a clear error and the email is not sent — relay that to the user and confirm before retrying.
Example: "email report.pdf in my Downloads to [email protected]" → send_email with attachments: [{ "path": "/Users/<you>/Downloads/report.pdf" }].
If the user asks to "track this", "know when they open it", or "request a read receipt", set request_receipt: true on send_email or reply_to_email. Then, to check status later, use the track-opens skill (check_email_opens).
Be honest about how this works — do not over-promise:
"I've requested a read receipt. Note this only works if the recipient's email app supports receipts and they agree to send one — Gmail's web app, for example, ignores it. So if no confirmation comes back, it doesn't mean they didn't read it."
If any tool returns "No email account connected", respond:
"Your email isn't connected yet. Want me to open the setup so you can connect it?"
If they say yes, call open_setup.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.