applySubscriptionChange
Apply a previously previewed subscription change. Same-tier seat changes update Stripe in place; cross-tier upgrades from Free return a hosted Checkout URL. Refuses target=free (use cancelSubscription) and target=enterprise (sales-led). Rate limit 5/h. Use only AFTER previewSubscriptionChange and...
This record as markdown: /tools/io-stablebaseline-sb/applysubscriptionchange.md
What applySubscriptionChange does on Stable Baseline
AI agents use applySubscriptionChange to commit financial operations through Stable Baseline, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
confirmation_token | string | Yes |
Parameters from the server's own tool schema.
Why applySubscriptionChange is rated Critical
This tool directly modifies a Stripe subscription, which commits financial obligations. It can upgrade/change subscription tiers, triggering billing charges. The explicit mention of Stripe, pricing confirmation, and checkout URLs confirms financial transactions are involved. Misuse could result in unauthorized charges to a customer's payment method, making this critical severity.
From the tool's definition Apply a previously previewed subscription change... update Stripe in place... cross-tier upgrades from Free return a hosted Checkout URL... Rate limit 5/h
Attacks that exploit this kind of access
The rule that runs applySubscriptionChange safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For applySubscriptionChange, this is the rule to start with:
Any call to applySubscriptionChange is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every applySubscriptionChange call is checked against it from then on.
Questions about applySubscriptionChange
Apply a previously previewed subscription change. Same-tier seat changes update Stripe in place; cross-tier upgrades from Free return a hosted Checkout URL. Refuses target=free (use cancelSubscription) and target=enterprise (sales-led). Rate limit 5/h. Use only AFTER previewSubscriptionChange and after the user confirms the preview's pricing — never call apply without the user seeing the preview first. It is categorised as a Financial tool in the Stable Baseline MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
applySubscriptionChange accepts 1 parameter: confirmation_token. Required: confirmation_token. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for applySubscriptionChange: 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 Stable Baseline. Nothing to install.
applySubscriptionChange 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 applySubscriptionChange 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 applySubscriptionChange. 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.
applySubscriptionChange is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
Across the catalogue