# swiftsign_check_status

Check the status of an envelope — who signed, who hasn't, download links. Works in both sandbox (sk_test_ keys) and live.

Agent View of the PolicyLayer registry record for `swiftsign_check_status`. HTML page: https://policylayer.com/tools/ca-swiftsign-mcp/swiftsign-check-status

## Facts

- Tool: `swiftsign_check_status`
- Server: Mcp (`https://swiftsign.ca/mcp`) — https://policylayer.com/tools/ca-swiftsign-mcp.md
- Homepage: https://github.com/shahdadk/swiftsign
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `envelopeId` | string | yes | The envelope ID to check |

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_check_status",
    "arguments": {
      "envelopeId": "<envelopeId>"
    }
  }
}
```

## Why swiftsign_check_status is rated Low

This tool retrieves and queries the state of an e-signature envelope without creating, modifying, or deleting any data. It is a pure information-retrieval operation. While it operates on financial/legal documents (e-signatures), the tool itself performs no financial transaction, does not modify records, and does not execute external operations.

From the tool's own definition: "Tool description explicitly states it 'Check[s] the status of an envelope' and provides 'download links' for information retrieval."

## Use case

AI agents call swiftsign_check_status to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "swiftsign_check_status": {}
  }
}
```

## 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_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_envelope` — Write — https://policylayer.com/tools/ca-swiftsign-mcp/swiftsign-send-envelope.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