# mail_send

Send a test email to verify mail configuration is working. Provide a subject, body text, and one or more recipient addresses.

Agent View of the PolicyLayer registry record for `mail_send`. HTML page: https://policylayer.com/tools/nasbridge/mail-send

## Facts

- Tool: `mail_send`
- Server: Nasbridge (`maverick0628/nasbridge`) — https://policylayer.com/tools/nasbridge.md
- Homepage: https://github.com/maverick0628/nasbridge
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "mail_send",
    "arguments": {}
  }
}
```

## Why mail_send is rated High

This tool triggers an external operation (sending an email) whose effects depend on arguments (subject, body, recipients). It does not simply read or write data within the system—it causes an external side effect by delivering email to specified recipients. Misuse could lead to spam or phishing emails being sent to arbitrary addresses.

From the tool's own definition: "Send a test email to verify mail configuration is working. Provide a subject, body text, and one or more recipient addresses."

## Use case

AI agents invoke mail_send to trigger actions in Nasbridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Nasbridge:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mail_send": {
      "limits": [
        {
          "counter": "mail_send_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Nasbridge (278)

- `acme_dns_authenticator_delete` — Destructive — https://policylayer.com/tools/nasbridge/acme-dns-authenticator-delete.md
- `alertservice_delete` — Destructive — https://policylayer.com/tools/nasbridge/alertservice-delete.md
- `api_key_delete` — Destructive — https://policylayer.com/tools/nasbridge/api-key-delete.md
- `app_delete` — Destructive — https://policylayer.com/tools/nasbridge/app-delete.md
- `app_rollback` — Destructive — https://policylayer.com/tools/nasbridge/app-rollback.md
- `boot_attach_disk` — Destructive — https://policylayer.com/tools/nasbridge/boot-attach-disk.md
- `boot_detach_disk` — Destructive — https://policylayer.com/tools/nasbridge/boot-detach-disk.md
- `bootenv_delete` — Destructive — https://policylayer.com/tools/nasbridge/bootenv-delete.md
- `certificate_delete` — Destructive — https://policylayer.com/tools/nasbridge/certificate-delete.md
- `cloud_backup_abort` — Destructive — https://policylayer.com/tools/nasbridge/cloud-backup-abort.md
- `cloud_backup_delete` — Destructive — https://policylayer.com/tools/nasbridge/cloud-backup-delete.md
- `cloudsync_credentials_delete` — Destructive — https://policylayer.com/tools/nasbridge/cloudsync-credentials-delete.md
- `cloudsync_delete` — Destructive — https://policylayer.com/tools/nasbridge/cloudsync-delete.md
- `cronjob_delete` — Destructive — https://policylayer.com/tools/nasbridge/cronjob-delete.md
- `dataset_delete` — Destructive — https://policylayer.com/tools/nasbridge/dataset-delete.md
- `directory_services_leave` — Destructive — https://policylayer.com/tools/nasbridge/directory-services-leave.md
- `disk_wipe` — Destructive — https://policylayer.com/tools/nasbridge/disk-wipe.md
- `group_delete` — Destructive — https://policylayer.com/tools/nasbridge/group-delete.md
- `initshutdown_delete` — Destructive — https://policylayer.com/tools/nasbridge/initshutdown-delete.md
- `iscsi_extent_delete` — Destructive — https://policylayer.com/tools/nasbridge/iscsi-extent-delete.md
- `iscsi_initiator_delete` — Destructive — https://policylayer.com/tools/nasbridge/iscsi-initiator-delete.md
- `iscsi_portal_delete` — Destructive — https://policylayer.com/tools/nasbridge/iscsi-portal-delete.md
- `iscsi_target_delete` — Destructive — https://policylayer.com/tools/nasbridge/iscsi-target-delete.md
- `iscsi_targetextent_delete` — Destructive — https://policylayer.com/tools/nasbridge/iscsi-targetextent-delete.md
- `keychaincredential_delete` — Destructive — https://policylayer.com/tools/nasbridge/keychaincredential-delete.md
- `network_interface_delete` — Destructive — https://policylayer.com/tools/nasbridge/network-interface-delete.md
- `network_rollback_changes` — Destructive — https://policylayer.com/tools/nasbridge/network-rollback-changes.md
- `network_static_route_delete` — Destructive — https://policylayer.com/tools/nasbridge/network-static-route-delete.md
- `nfs_share_delete` — Destructive — https://policylayer.com/tools/nasbridge/nfs-share-delete.md
- `pool_export` — Destructive — https://policylayer.com/tools/nasbridge/pool-export.md
- …and 248 more: https://policylayer.com/tools/nasbridge.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=nasbridge · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/nasbridge