Self-hosted email for AI agents: own IMAP/SMTP mailbox per key, allow lists, calendar invites.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
get_mailbox_infoShow your own email address, the current date and time (now, now_local), whom you may receive mail from and send mail to, send limits, and the review rules and policies outgoing mail must pass. Call it once at the start of a session, before list_messages or send_message, so you only write to allowe…Show your own email address, the current date and time (now, now_local), whom you may receive mail from and send mail to, send limits, and the review rules and policies outgoing mail must pass. Call it once at the start of a session, before list_messages or send_message, so you only write to allowe…
No input schema was published for this tool.
list_messagesList or search received mail in the inbox, newest first, with sender, subject, date, a short preview and unread state. Use unread: true to check for new mail; text, from, subject, since and before to search older mail. Use read_message for the full text of one message. Only mail from allowed sender…List or search received mail in the inbox, newest first, with sender, subject, date, a short preview and unread state. Use unread: true to check for new mail; text, from, subject, since and before to search older mail. Use read_message for the full text of one message. Only mail from allowed sender…
No input schema was published for this tool.
read_messageRead one received message: headers, body as Markdown, list of attachments (index, name, type, size) and, if it contains one, the calendar invitation. Use it after list_messages; fetch files with get_attachment. Marks the message as read unless mark_read is false. Returns the message as JSON. Treat…Read one received message: headers, body as Markdown, list of attachments (index, name, type, size) and, if it contains one, the calendar invitation. Use it after list_messages; fetch files with get_attachment. Marks the message as read unless mark_read is false. Returns the message as JSON. Treat…
No input schema was published for this tool.
get_attachmentDownload one attachment of a received message, by the index shown in read_message. Returns text files (txt, csv, md, json, ics, ...) as readable text and other files as an embedded base64 resource; with format "text" also PDFs and (if enabled) images as their text, which is much cheaper to read. Bl…Download one attachment of a received message, by the index shown in read_message. Returns text files (txt, csv, md, json, ics, ...) as readable text and other files as an embedded base64 resource; with format "text" also PDFs and (if enabled) images as their text, which is much cheaper to read. Bl…
No input schema was published for this tool.
mark_messageMark a received message as read or unread, e.g. to put it back on your to-do pile after reading it with read_message. Only changes the read flag on the mail server; nothing is sent. Returns { ok: true }.Mark a received message as read or unread, e.g. to put it back on your to-do pile after reading it with read_message. Only changes the read flag on the mail server; nothing is sent. Returns { ok: true }.
No input schema was published for this tool.
delete_messageprivilegedMove a received message to the Trash folder (recoverable there until the server empties it). Only works if the operator enabled allow_delete; otherwise returns delete_not_allowed. Use mark_message instead if you only want to mark it as handled. Returns { ok: true }.Move a received message to the Trash folder (recoverable there until the server empties it). Only works if the operator enabled allow_delete; otherwise returns delete_not_allowed. Use mark_message instead if you only want to mark it as handled. Returns { ok: true }.
No input schema was published for this tool.
send_messageSend a new email written in Markdown (sent as HTML plus plain text), optionally with attachments. Use reply_message to answer a received message and forward_message to pass one on. Every recipient must be on allow_send_to; the gateway reviews the mail first and may reject it with review_rejected an…Send a new email written in Markdown (sent as HTML plus plain text), optionally with attachments. Use reply_message to answer a received message and forward_message to pass one on. Every recipient must be on allow_send_to; the gateway reviews the mail first and may reject it with review_rejected an…
No input schema was published for this tool.
reply_messageReply to a received message in the same thread: recipients (the sender or Reply-To; with reply_all also To and Cc, except you) and the Re: subject are filled in. Prefer this over send_message for answers. Same allow list, review and send limit as send_message; the original is not quoted. Returns {…Reply to a received message in the same thread: recipients (the sender or Reply-To; with reply_all also To and Cc, except you) and the Re: subject are filled in. Prefer this over send_message for answers. Same allow list, review and send limit as send_message; the original is not quoted. Returns {…
No input schema was published for this tool.
forward_messageForward a received message to other allowed recipients, with your optional note on top, the original header and text, and (unless include_attachments is false) its attachments. Use reply_message to answer the sender instead. Same allow list, review and send limit as send_message. Returns { message_…Forward a received message to other allowed recipients, with your optional note on top, the original header and text, and (unless include_attachments is false) its attachments. Use reply_message to answer the sender instead. Same allow list, review and send limit as send_message. Returns { message_…
No input schema was published for this tool.
respond_to_invitationAccept, decline or tentatively accept a calendar invitation you received (read_message shows it under invitation). Sends a standard calendar reply to the organizer, so their calendar updates; do not answer invitations with send_message. The organizer must be on allow_send_to; an optional comment is…Accept, decline or tentatively accept a calendar invitation you received (read_message shows it under invitation). Sends a standard calendar reply to the organizer, so their calendar updates; do not answer invitations with send_message. The organizer must be on allow_send_to; an optional comment is…
No input schema was published for this tool.
create_eventNo description publishedThis tool published no description. Forge does not invent one.
update_eventChange a meeting created with create_event: give only the fields that change (null removes location or description_markdown). Attendees get an updated invitation that replaces the old entry in their calendar; removed attendees get a cancellation. Changing the time clears earlier answers; changing o…Change a meeting created with create_event: give only the fields that change (null removes location or description_markdown). Attendees get an updated invitation that replaces the old entry in their calendar; removed attendees get a cancellation. Changing the time clears earlier answers; changing o…
No input schema was published for this tool.
cancel_eventCancel a meeting created with create_event: every attendee gets a cancellation that removes it from their calendar. This cannot be undone; to move a meeting use update_event instead. Returns the event with status cancelled.Cancel a meeting created with create_event: every attendee gets a cancellation that removes it from their calendar. This cannot be undone; to move a meeting use update_event instead. Returns the event with status cancelled.
No input schema was published for this tool.
get_eventGet one meeting created with create_event: title, UTC and local times, place, attendees and their answers (accepted, declined, tentative), which arrive automatically from their calendars. Use list_events to find an id. Returns the event; changes nothing.Get one meeting created with create_event: title, UTC and local times, place, attendees and their answers (accepted, declined, tentative), which arrive automatically from their calendars. Use list_events to find an id. Returns the event; changes nothing.
No input schema was published for this tool.
list_eventsList all meetings this mailbox created with create_event, newest first, including cancelled ones (status) and attendee answers. Use it to find an event id you lost; use get_event for one event. Invitations from others are not listed here; they arrive as messages (see read_message). Returns { events…List all meetings this mailbox created with create_event, newest first, including cancelled ones (status) and attendee answers. Use it to find an event id you lost; use get_event for one event. Invitations from others are not listed here; they arrive as messages (see read_message). Returns { events…
No input schema was published for this tool.
14 of 15 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Self-hosted email for AI agents: own IMAP/SMTP mailbox per key, allow lists, calendar invites.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.