# swiftsign_send_envelope

Send a document for e-signature. Accepts PDF as base64, recipients, and field placement. Sandbox keys (sk_test_) send immediately (watermarked test mail). LIVE keys create a DRAFT and return it for human review unless confirm: true — nothing is emailed until confirmed. Field placement: page+x+y (percent, top-left origin) OR an anchor string, not both. After everyone signs, retrieve the sealed PDF with swiftsign_download_signed_pdf.

Agent View of the PolicyLayer registry record for `swiftsign_send_envelope`. HTML page: https://policylayer.com/tools/ca-swiftsign-mcp/swiftsign-send-envelope

## Facts

- Tool: `swiftsign_send_envelope`
- Server: Mcp (`https://swiftsign.ca/mcp`) — https://policylayer.com/tools/ca-swiftsign-mcp.md
- Homepage: https://github.com/shahdadk/swiftsign
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 6 (4 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `fields` | array | yes | Signing fields to place on documents |
| `confirm` | boolean | no | Set true to dispatch immediately on a LIVE key (sk_live_/sk_oat_). Without it, live envelopes are created as DRAFT and returned for human review before anything |
| `message` | string | no | Optional message to include |
| `subject` | string | yes | Email subject / document title |
| `documents` | array | yes | PDF documents to send |
| `recipients` | array | yes | People who need to sign or receive a copy |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "swiftsign_send_envelope",
    "arguments": {
      "fields": [],
      "subject": "<subject>",
      "documents": [],
      "recipients": []
    }
  }
}
```

## Why swiftsign_send_envelope is rated Medium

This tool sends legal e-signature requests to external recipients, creating binding signature envelopes. While it can be reversed (voided) before completion, it initiates external communications and creates legally significant documents. With 'confirm: true' on a live key, it sends immediately to recipients — a significant Write action with real-world consequences.

From the tool's own definition: "Send a document for e-signature. Accepts PDF as base64, recipients, and field placement. Sandbox keys send immediately (watermarked test mail). LIVE keys create a DRAFT and return it for human review unless confirm: true — nothing is emailed until confirmed."

Risk signals: High parameter count (23 properties)

## Use case

AI agents use swiftsign_send_envelope to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "swiftsign_send_envelope": {
      "limits": [
        {
          "counter": "swiftsign_send_envelope_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp (9)

- `swiftsign_void_envelope` — Destructive — https://policylayer.com/tools/ca-swiftsign-mcp/swiftsign-void-envelope.md
- `swiftsign_create_embedded_url` — Execute — https://policylayer.com/tools/ca-swiftsign-mcp/swiftsign-create-embedded-url.md
- `swiftsign_upgrade` — Financial — https://policylayer.com/tools/ca-swiftsign-mcp/swiftsign-upgrade.md
- `swiftsign_check_status` — Read — https://policylayer.com/tools/ca-swiftsign-mcp/swiftsign-check-status.md
- `swiftsign_download_signed_pdf` — Read — https://policylayer.com/tools/ca-swiftsign-mcp/swiftsign-download-signed-pdf.md
- `swiftsign_list_envelopes` — Read — https://policylayer.com/tools/ca-swiftsign-mcp/swiftsign-list-envelopes.md
- `swiftsign_list_templates` — Read — https://policylayer.com/tools/ca-swiftsign-mcp/swiftsign-list-templates.md
- `swiftsign_confirm_send` — Write — https://policylayer.com/tools/ca-swiftsign-mcp/swiftsign-confirm-send.md
- `swiftsign_send_from_template` — Write — https://policylayer.com/tools/ca-swiftsign-mcp/swiftsign-send-from-template.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=ca-swiftsign-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ca-swiftsign-mcp