mcp-mail-server
User review for permanent message deletion through mcp-mail-server.
Conservative operation knowledge compiled from a contributor inventory.
mcp.mail-server · v1.0.0 · Specialized tools
- Protection rules
- 0
- Permission checks
- 1
- Mapped commands
- 1
Overview
What this coverage does
Conservative operation knowledge compiled from a contributor inventory.
Key facts
- Catalog ID
mcp.mail-server- Version
- v1.0.0
- Kind
- MCP server
- Category
- Specialized tools
- Protection rules
- 0
- Permission checks
- 1
- Mapped commands
- 1
- Maintainer
- Community contributor(community, provenance recorded)
- Source commit
- d5cec22
- Protection model
- External · opt-in
External coverage. It must be enabled through Guard controls; this page does not activate it.
Stated limits
- Coverage focuses on permanent deletion through delete_message and delete_messages; other mail mutations retain host policy.
- Automatic read allowances require the reviewed npx launcher, stdio transport, registry package selectors and default package-source evidence without configured package-manager overrides.
- Default package-source evidence does not attest to installed code or the contents of ambient package-manager configuration files.
- A publisher profile is not a security certification or an endorsement by HOL.
mcpemailimapapprovalCommand mapping
Every command this extension recognizes, with the catalog default floor Guard applies before workspace policy. Search the table, then open an operation for safe variants and the permission ID.
No per-command matchers are published for this listing. Coverage is described by the reviewed rule count, permission checks, and the surrounding Guard policy.
Tool state mapping
| Tool | Guard state |
|---|---|
| check_connection | Inherit policy |
| continue_email_thread | Inherit policy |
| delete_message | Review |
| delete_messages | Review |
| find_unreplied_messages | Inherit policy |
| get_message | Inherit policy |
| get_messages | Inherit policy |
| list_mailboxes | Allowed |
| move_message | Inherit policy |
| move_messages | Inherit policy |
| reply_to_email | Inherit policy |
| save_attachment | Inherit policy |
| search_messages | Allowed |
| send_email | Inherit policy |
| other | Inherit policy |
Runtime identity
- Catalog ID
- mcp.mail-server
- Guard enforcement ID
- command.mcp-mail-server
- Source path
- contributions/mcp-servers/mcp.mail-server.json
- Contribution digest
sha256…d5475d
Mapped executables
npxAction classes
mcp mailxhserver toolTechnical profile
No independent profile published
This extension has no current independent technical profile. Catalog facts and any legacy launch remain separate and are not presented as profile evidence.
FAQ
Frequently asked questions
Conservative operation knowledge compiled from a contributor inventory. The listing declares 0 rules and 1 permission check, with per-tool mapping for 15 tools. No per-command matchers are published for this listing.. Coverage is limited to these reviewed operations and the surrounding Guard policy.
External · opt-in: External coverage. It must be enabled through Guard controls; this page does not activate it. Enabling state is always controlled through Guard policy, never from this directory.
This listing entered the catalog as a community contribution through a public pull request with recorded provenance, with public credit to @yunfeizhu, and 1 GitHub maintainer is recorded on the listing. Credit is attribution only. A verified publisher profile and the claim flow verify authority separately; neither is an upstream endorsement or a HOL safety certification.
No. Every listing documents source, activation model, maintainer identity, and stated limitations so you can evaluate coverage before enabling it. Review the stated limitations and the exact source tree before relying on any single control.
This listing does not publish per-command matchers. Exact behavior follows your Guard policy combined with this entry's 0 rules and 1 permission check.
External coverage. It must be enabled through Guard controls; this page does not activate it. Enablement is managed through your workspace's Guard policy and controls — never from this directory. Open the install guidance for the setup flow, then adjust the MCP coverage for mcp.mail-server in Guard's policy surface.
The matching action is stopped at Guard's pre-action boundary before it executes, and the decision is recorded with evidence your workspace can review. Exact behavior follows your Guard policy combined with this entry's 0 rules and 1 permission check.
No. Guard is local-first: interception, decisions, and evidence stay on your machine unless your workspace explicitly configures cloud features. This page is documentation only — it never executes a command or changes protection state.
Guard runs locally alongside the major AI coding agents and MCP-capable harnesses, so this coverage applies wherever Guard intercepts actions. See the supported harness guides at https://hol.org/guard/harnesses for per-tool approval behavior and limitations.
Guard has a free local tier that includes command interception, evidence, and the policy controls this listing documents. Team plans add shared policy, review queues, and audit surfaces. Current plans: https://hol.org/guard/pricing
Open an issue or pull request against the hol-guard repository, where the canonical catalog lives: https://github.com/hashgraph-online/hol-guard Listings are corrected through the same public review process that adds them.
Yes. Community extensions are merged through public pull requests with recorded provenance, and you can claim the publisher page for a contribution you maintain through the Publisher Studio.
The command mapping table is the audit trail for covered commands and catalog default floors. Pair it with the reviewed rule and permission counts, the per-tool state mapping, and the exact source tree linked from View exact source at the reviewed commit. Guard records enforcement decisions with evidence locally, so what ships matches what you reviewed.