create_plan_upgrade_link
Create a Stripe Checkout link for a new paid subscription, or a Stripe Billing Portal link for an existing Stripe subscription. Use only after the user explicitly asks to upgrade or fix billing.
This record as markdown: /tools/io-favcrm-favcrm/create-plan-upgrade-link.md
What create_plan_upgrade_link does on FavCRM
AI agents use create_plan_upgrade_link to commit financial operations through FavCRM, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
planId | string | — | Target plan ID. Use list_plan_options first if unknown. |
confirm | boolean | — | Required true to create a Stripe-hosted payment or billing link. |
planCode | string | — | Target plan code, e.g. favcrm-lite. Either planId or planCode is required. |
returnUrl | string | — | Where Stripe should return after checkout/portal. Defaults to merchant billing settings. |
billingCycle | string | — |
Parameters from the server's own tool schema.
Why create_plan_upgrade_link is rated Critical
This tool initiates or modifies paid subscription commitments via Stripe, directly involving financial obligations. Misuse could result in unwanted subscription charges or billing changes, making it Financial category with critical severity.
From the tool's definition Create a Stripe Checkout link for a new paid subscription, or a Stripe Billing Portal link for an existing Stripe subscription
Attacks that exploit this kind of access
The rule that runs create_plan_upgrade_link safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_plan_upgrade_link, this is the rule to start with:
Any call to create_plan_upgrade_link is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every create_plan_upgrade_link call is checked against it from then on.
Questions about create_plan_upgrade_link
Create a Stripe Checkout link for a new paid subscription, or a Stripe Billing Portal link for an existing Stripe subscription. Use only after the user explicitly asks to upgrade or fix billing. It is categorised as a Financial tool in the FavCRM MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
create_plan_upgrade_link accepts 5 parameters: planId, confirm, planCode, returnUrl, billingCycle. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for create_plan_upgrade_link: 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 FavCRM. Nothing to install.
create_plan_upgrade_link 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 create_plan_upgrade_link 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 create_plan_upgrade_link. 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.
create_plan_upgrade_link is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
Across the catalogue