purchaseCreditPackage
Apply a credit-package quote by creating a hosted Stripe Checkout session. Returns checkout_url + session_id. Refuses if catalogued price has drifted. Rate limit 5/h. Use only AFTER quoteCreditPackage and after the user confirms — never start a checkout without the quote step first.
This record as markdown: /tools/io-stablebaseline-sb/purchasecreditpackage.md
What purchaseCreditPackage does on Stable Baseline
AI agents use purchaseCreditPackage 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 |
|---|---|---|---|
quote_token | string | Yes |
Parameters from the server's own tool schema.
Why purchaseCreditPackage is rated Critical
This tool initiates a real financial transaction via Stripe Checkout, committing the user to a monetary payment for a credit package. It directly moves money or creates a financial obligation, placing it firmly in the Financial category. Misuse by an AI agent could result in unauthorized purchases, making the severity critical.
From the tool's definition purchaseCreditPackage, 'creating a hosted Stripe Checkout session', 'never start a checkout without the quote step first', 'Apply a credit-package quote'
Attacks that exploit this kind of access
The rule that runs purchaseCreditPackage 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 purchaseCreditPackage, this is the rule to start with:
Any call to purchaseCreditPackage 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 purchaseCreditPackage call is checked against it from then on.
Questions about purchaseCreditPackage
Apply a credit-package quote by creating a hosted Stripe Checkout session. Returns checkout_url + session_id. Refuses if catalogued price has drifted. Rate limit 5/h. Use only AFTER quoteCreditPackage and after the user confirms — never start a checkout without the quote step 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.
purchaseCreditPackage accepts 1 parameter: quote_token. Required: quote_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 purchaseCreditPackage: 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.
purchaseCreditPackage 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 purchaseCreditPackage 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 purchaseCreditPackage. 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.
purchaseCreditPackage 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