swiftsign_send_envelope

SERVERMcp SOURCEhttps://swiftsign.ca/mcp

Medium RISK CLASS

Category Write

Parameters 64 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ca-swiftsign-mcp/swiftsign-send-envelope.md

WHAT IT DOES

What swiftsign_send_envelope does on Mcp

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.

Parameter	Type	Required	Description
`fields`	array	Yes	Signing fields to place on documents
`confirm`	boolean	—	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	—	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.

RISK

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 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 signalsHigh parameter count (23 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs swiftsign_send_envelope safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For swiftsign_send_envelope, this is the rule to start with:

swiftsign_send_envelope Rate-limited

swiftsign_send_envelope stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every swiftsign_send_envelope call is checked against it from then on.

FAQ

Questions about swiftsign_send_envelope

What does the swiftsign_send_envelope tool do? +

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. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does swiftsign_send_envelope accept? +

swiftsign_send_envelope accepts 6 parameters: fields, confirm, message, subject, documents, recipients. Required: fields, subject, documents, recipients. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on swiftsign_send_envelope? +

Register the MCP server in PolicyLayer and add a rule for swiftsign_send_envelope: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp. Nothing to install.

What risk level is swiftsign_send_envelope? +

swiftsign_send_envelope is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit swiftsign_send_envelope? +

Yes. Add a rate_limit block to the swiftsign_send_envelope rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block swiftsign_send_envelope completely? +

Set action: deny in the PolicyLayer policy for swiftsign_send_envelope. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides swiftsign_send_envelope? +

swiftsign_send_envelope is provided by the MCP server (https://swiftsign.ca/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 10 tools →

Across the catalogue

sms_send on Twilio SMS MCP Server →send-draft on Meme MCP Server →mail_send_draft on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →