This record as markdown: /tools/ca-swiftsign-mcp/swiftsign-create-embedded-url.md
What swiftsign_create_embedded_url does on Mcp
AI agents invoke swiftsign_create_embedded_url to trigger actions in Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
returnUrl | string | — | URL to redirect the signer to after they finish |
envelopeId | string | Yes | The envelope ID |
recipientId | string | Yes | The recipient ID within that envelope |
Parameters from the server's own tool schema.
Why swiftsign_create_embedded_url is rated High
This tool generates (mints) a time-limited signing URL, which is an external operation that creates an active signing session for a recipient. It doesn't just read data — it triggers the creation of a functional signing link that can be used to execute a legally binding e-signature workflow.
From the tool's definition Mint a short-lived embedded signing URL for a recipient (30-minute expiry). Returns a url to embed plus its expiresAt.
Attacks that exploit this kind of access
The rule that runs swiftsign_create_embedded_url 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_create_embedded_url, this is the rule to start with:
swiftsign_create_embedded_url stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every swiftsign_create_embedded_url call is checked against it from then on.
Questions about swiftsign_create_embedded_url
Mint a short-lived embedded signing URL for a recipient (30-minute expiry). Returns a url to embed plus its expiresAt. The envelope must already be SENT. Works in both sandbox (sk_test_ keys) and live. It is categorised as a Execute tool in the Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
swiftsign_create_embedded_url accepts 3 parameters: returnUrl, envelopeId, recipientId. Required: envelopeId, recipientId. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for swiftsign_create_embedded_url: 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.
swiftsign_create_embedded_url is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the swiftsign_create_embedded_url 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.
Set action: deny in the PolicyLayer policy for swiftsign_create_embedded_url. 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.
swiftsign_create_embedded_url 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