swiftsign_upgrade
Initiate the upgrade to PRO ($15/mo flat). Returns a Stripe checkout_url that a human opens once to add a card — agents cannot complete the payment themselves. Moves the account from sandbox (sk_test_) to live sends. Returns status 'updated' if already on the plan.
This record as markdown: /tools/ca-swiftsign-mcp/swiftsign-upgrade.md
What swiftsign_upgrade does on Mcp
AI agents use swiftsign_upgrade to commit financial operations through Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
plan | string | — | Plan to upgrade to (default PRO) |
Parameters from the server's own tool schema.
Why swiftsign_upgrade is rated Critical
This tool initiates a financial subscription commitment of $15/month by starting a Stripe checkout flow. While a human must complete the payment, the tool initiates the financial obligation and transitions the account to a paid live plan. The financial category applies because it commits financial obligations.
From the tool's definition Initiate the upgrade to PRO ($15/mo flat)... Stripe checkout_url... add a card... Moves the account from sandbox (sk_test_) to live sends
Attacks that exploit this kind of access
The rule that runs swiftsign_upgrade 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_upgrade, this is the rule to start with:
Any call to swiftsign_upgrade is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every swiftsign_upgrade call is checked against it from then on.
Questions about swiftsign_upgrade
Initiate the upgrade to PRO ($15/mo flat). Returns a Stripe checkout_url that a human opens once to add a card — agents cannot complete the payment themselves. Moves the account from sandbox (sk_test_) to live sends. Returns status 'updated' if already on the plan. It is categorised as a Financial tool in the Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
swiftsign_upgrade accepts 1 parameter: plan. 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_upgrade: 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_upgrade is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the swiftsign_upgrade 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_upgrade. 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_upgrade 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