swiftsign_send_from_template

SERVERMcp SOURCEhttps://swiftsign.ca/mcp

Medium RISK CLASS

Category Write

Parameters 52 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-from-template.md

WHAT IT DOES

What swiftsign_send_from_template does on Mcp

AI agents use swiftsign_send_from_template 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
`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	—	Email subject / document title
`templateId`	string	Yes	The template ID to send from
`roleAssignments`	object	Yes	Map of template role name → signer { name, email }

Parameters from the server's own tool schema.

RISK

Why swiftsign_send_from_template is rated Medium

This tool creates or modifies document state by instantiating an envelope from a template and assigning signers. While it can trigger email sends, the primary effect is creation of a reversible record. It falls under Write rather than Execute because it doesn't run arbitrary code or shell commands—it follows a structured workflow within the e-signature platform.

From the tool's definition Tool 'sends an envelope' and 'nothing is emailed until confirmed' — creates a new envelope document state that is reversible (can be voided via swiftsign_void_envelope).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

swiftsign_send_from_template Rate-limited

swiftsign_send_from_template 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_from_template": {
      "limits": [
        {
          "counter": "swiftsign_send_from_template_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_from_template call is checked against it from then on.

FAQ

Questions about swiftsign_send_from_template

What does the swiftsign_send_from_template tool do? +

Send an envelope from a saved template by assigning signers to roles. Sandbox keys (sk_test_) send immediately; LIVE keys create a DRAFT for human review unless confirm: true — nothing is emailed until confirmed. 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_from_template accept? +

swiftsign_send_from_template accepts 5 parameters: confirm, message, subject, templateId, roleAssignments. Required: templateId, roleAssignments. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on swiftsign_send_from_template? +

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

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

Can I rate-limit swiftsign_send_from_template? +

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

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

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