Multi-account Gmail on a Cloudflare Worker you deploy yourself: read, send, reply, labels, threads
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.
whoamiNo description publishedThis tool published no description. Forge does not invent one.
search_messagesNo description publishedThis tool published no description. Forge does not invent one.
get_messageNo description publishedThis tool published no description. Forge does not invent one.
get_threadNo description publishedThis tool published no description. Forge does not invent one.
list_labelsNo description publishedThis tool published no description. Forge does not invent one.
modify_labelsNo description publishedThis tool published no description. Forge does not invent one.
trash_messageNo description publishedThis tool published no description. Forge does not invent one.
create_draftNo description publishedThis tool published no description. Forge does not invent one.
update_draftNo description publishedThis tool published no description. Forge does not invent one.
send_draftNo description publishedThis tool published no description. Forge does not invent one.
delete_draftprivilegedNo description publishedThis tool published no description. Forge does not invent one.
list_draftsNo description publishedThis tool published no description. Forge does not invent one.
stage_attachment_beginNo description publishedThis tool published no description. Forge does not invent one.
stage_attachment_appendNo description publishedThis tool published no description. Forge does not invent one.
stage_attachment_finishNo description publishedThis tool published no description. Forge does not invent one.
send_messageNo description publishedThis tool published no description. Forge does not invent one.
reply_allNo description publishedThis tool published no description. Forge does not invent one.
forward_messageNo description publishedThis tool published no description. Forge does not invent one.
get_attachmentNo description publishedThis tool published no description. Forge does not invent one.
untrash_messageNo description publishedThis tool published no description. Forge does not invent one.
modify_thread_labelsNo description publishedThis tool published no description. Forge does not invent one.
trash_threadNo description publishedThis tool published no description. Forge does not invent one.
untrash_threadNo description publishedThis tool published no description. Forge does not invent one.
batch_modify_messagesNo description publishedThis tool published no description. Forge does not invent one.
create_labelNo description publishedThis tool published no description. Forge does not invent one.
update_labelNo description publishedThis tool published no description. Forge does not invent one.
delete_labelprivilegedNo description publishedThis tool published no description. Forge does not invent one.
0 of 27 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.
Multi-account Gmail on a Cloudflare Worker you deploy yourself: read, send, reply, labels, threads
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.