swiftsign_check_status

Check the status of an envelope — who signed, who hasn't, download links. Works in both sandbox (sk_test_ keys) and live.

SERVERMcp SOURCEhttps://swiftsign.ca/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ca-swiftsign-mcp/swiftsign-check-status.md

WHAT IT DOES

What swiftsign_check_status does on Mcp

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

Parameter	Type	Required	Description
`envelopeId`	string	Yes	The envelope ID to check

Parameters from the server's own tool schema.

RISK

Why swiftsign_check_status is rated Low

This tool retrieves and queries the state of an e-signature envelope without creating, modifying, or deleting any data. It is a pure information-retrieval operation. While it operates on financial/legal documents (e-signatures), the tool itself performs no financial transaction, does not modify records, and does not execute external operations.

From the tool's definition Tool description explicitly states it 'Check[s] the status of an envelope' and provides 'download links' for information retrieval.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

swiftsign_check_status Allowed

swiftsign_check_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "swiftsign_check_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about swiftsign_check_status

What does the swiftsign_check_status tool do? +

Check the status of an envelope — who signed, who hasn't, download links. Works in both sandbox (sk_test_ keys) and live. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does swiftsign_check_status accept? +

swiftsign_check_status 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_check_status? +

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

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

Can I rate-limit swiftsign_check_status? +

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

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

swiftsign_check_status 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →