swiftsign_confirm_send

SERVERMcp SOURCEhttps://swiftsign.ca/mcp

Medium RISK CLASS

Category Write

Parameters 11 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-confirm-send.md

WHAT IT DOES

What swiftsign_confirm_send does on Mcp

AI agents use swiftsign_confirm_send 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
`envelopeId`	string	Yes	The DRAFT envelope ID to dispatch

Parameters from the server's own tool schema.

RISK

Why swiftsign_confirm_send is rated Medium

This tool modifies state (DRAFT→SENT) and triggers external notifications (emails to signers), which are reversible side effects. It does not execute arbitrary code, delete data, or move money. While it initiates a business-critical e-signature workflow with potential contractual implications, the action itself is a standard write operation.

From the tool's definition Tool description states 'Dispatch a DRAFT envelope' and 'This emails the signers.' The action transitions an envelope from draft_pending_confirmation to sent status, creating email notifications and initiating a signature workflow.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs swiftsign_confirm_send 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_confirm_send, this is the rule to start with:

swiftsign_confirm_send Rate-limited

swiftsign_confirm_send 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_confirm_send": {
      "limits": [
        {
          "counter": "swiftsign_confirm_send_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_confirm_send call is checked against it from then on.

FAQ

Questions about swiftsign_confirm_send

What does the swiftsign_confirm_send tool do? +

Dispatch a DRAFT envelope — use after a human has reviewed an envelope that swiftsign_send_envelope or swiftsign_send_from_template returned as draft_pending_confirmation. This emails the signers. Does NOT work on envelopes already SENT/COMPLETED/VOIDED. 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_confirm_send accept? +

swiftsign_confirm_send accepts 1 parameter: envelopeId. Required: envelopeId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on swiftsign_confirm_send? +

Register the MCP server in PolicyLayer and add a rule for swiftsign_confirm_send: 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_confirm_send? +

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

Can I rate-limit swiftsign_confirm_send? +

Yes. Add a rate_limit block to the swiftsign_confirm_send 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_confirm_send completely? +

Set action: deny in the PolicyLayer policy for swiftsign_confirm_send. 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_confirm_send? +

swiftsign_confirm_send 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 →