swiftsign_download_signed_pdf

Download the completed, sealed PDF (or its Certificate of Completion) for an envelope. Only works once status is COMPLETED — run swiftsign_check_status first. Does NOT work on DRAFT or SENT envelopes; nothing has been signed yet on those.

SERVERMcp SOURCEhttps://swiftsign.ca/mcp
Low RISK CLASS
Category Read
Parameters 41 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ca-swiftsign-mcp/swiftsign-download-signed-pdf.md

What swiftsign_download_signed_pdf does on Mcp

AI agents call swiftsign_download_signed_pdf 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.

ParameterTypeRequiredDescription
document number Which document to download when an envelope has several (0-based, default 0)
envelopeId string Yes The envelope ID (must be COMPLETED)
outputPath string Where to save the file (default: ./swiftsign-<id>.pdf). Ignored on the hosted endpoint, which returns base64.
certificate boolean If true, download the Certificate of Completion (audit trail) instead of the signed document

Parameters from the server's own tool schema.

Why swiftsign_download_signed_pdf is rated Low

This tool retrieves and queries signed document data without any side effects. It does not create, modify, delete, or execute operations. It is purely a data retrieval function that accesses already-finalized signed documents, making it a Read category tool with low severity since retrieving signed PDFs poses minimal risk compared to other operations on this signing platform.

From the tool's definition Downloads a completed, sealed PDF or Certificate of Completion; explicitly described as read-only retrieval with no modification or deletion: 'Download the completed, sealed PDF'.

Questions about swiftsign_download_signed_pdf

What does the swiftsign_download_signed_pdf tool do? +

Download the completed, sealed PDF (or its Certificate of Completion) for an envelope. Only works once status is COMPLETED — run swiftsign_check_status first. Does NOT work on DRAFT or SENT envelopes; nothing has been signed yet on those. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does swiftsign_download_signed_pdf accept? +

swiftsign_download_signed_pdf accepts 4 parameters: document, envelopeId, outputPath, certificate. 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_download_signed_pdf? +

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

swiftsign_download_signed_pdf is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit swiftsign_download_signed_pdf? +

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

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

swiftsign_download_signed_pdf 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.

More on , and thousands of servers like it.

This server

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.