reactivateSubscription
Reactivate a subscription that was scheduled to cancel at period end (clears cancel_at_period_end). Rate limit 5/h. Use when the user asks to reactivate, uncancel, restore, or keep their subscription after they previously cancelled but before the period ends.
This record as markdown: /tools/io-stablebaseline-sb/reactivatesubscription.md
What reactivateSubscription does on Stable Baseline
AI agents use reactivateSubscription 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 |
|---|---|---|---|
organisation_id | string | Yes |
Parameters from the server's own tool schema.
Why reactivateSubscription is rated Critical
This tool modifies a subscription's billing status by reversing a cancellation, which directly commits the user to ongoing financial obligations. It falls squarely in the Financial category as it affects payment/subscription state. Severity is high because misuse could reinstate unwanted recurring charges without the user's explicit consent.
From the tool's definition Reactivate a subscription that was scheduled to cancel at period end (clears cancel_at_period_end)
Attacks that exploit this kind of access
The rule that runs reactivateSubscription 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 reactivateSubscription, this is the rule to start with:
Any call to reactivateSubscription 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 reactivateSubscription call is checked against it from then on.
Questions about reactivateSubscription
Reactivate a subscription that was scheduled to cancel at period end (clears cancel_at_period_end). Rate limit 5/h. Use when the user asks to reactivate, uncancel, restore, or keep their subscription after they previously cancelled but before the period ends. 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.
reactivateSubscription accepts 1 parameter: organisation_id. Required: organisation_id. 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 reactivateSubscription: 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.
reactivateSubscription 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 reactivateSubscription 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 reactivateSubscription. 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.
reactivateSubscription 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