getCustomerPortalLink
Mint a single-use Stripe Customer Portal URL for self-serve billing changes. return_url defaults to https://app.stablebaseline.io/settings/billing and must be on a stablebaseline.* host.
This record as markdown: /tools/io-stablebaseline-sb/getcustomerportallink.md
What getCustomerPortalLink does on Stable Baseline
AI agents use getCustomerPortalLink 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 |
|---|---|---|---|
return_url | string | — | |
organisation_id | string | Yes |
Parameters from the server's own tool schema.
Why getCustomerPortalLink is rated Critical
This tool generates access to Stripe's Customer Portal, which allows users to make billing changes such as updating payment methods, modifying subscriptions, or cancelling plans. This directly touches financial obligations and billing infrastructure. Misuse could allow an AI agent to redirect billing management to an attacker-controlled session or trigger unintended subscription changes.
From the tool's definition Mint a single-use Stripe Customer Portal URL for self-serve billing changes
Attacks that exploit this kind of access
The rule that runs getCustomerPortalLink 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 getCustomerPortalLink, this is the rule to start with:
Any call to getCustomerPortalLink 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 getCustomerPortalLink call is checked against it from then on.
Questions about getCustomerPortalLink
Mint a single-use Stripe Customer Portal URL for self-serve billing changes. return_url defaults to https://app.stablebaseline.io/settings/billing and must be on a stablebaseline.* host. 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.
getCustomerPortalLink accepts 2 parameters: return_url, 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 getCustomerPortalLink: 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.
getCustomerPortalLink 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 getCustomerPortalLink 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 getCustomerPortalLink. 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.
getCustomerPortalLink 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