listCreditPurchases
List credit-purchase history for an organisation, newest first. Status, credits purchased, bonus, amount paid in AUD cents, completion timestamp. Stripe IDs stripped.
This record as markdown: /tools/io-stablebaseline-sb/listcreditpurchases.md
What listCreditPurchases does on Stable Baseline
AI agents call listCreditPurchases to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max rows (default 50, max 200). |
offset | number | — | Pagination offset (default 0). |
organisation_id | string | Yes | UUID of the organisation. Must match the credential's organisation. |
Parameters from the server's own tool schema.
Why listCreditPurchases is rated Low
This tool retrieves historical financial transaction records for an organisation. Although it concerns financial data (credit purchases and amounts paid), it performs no financial operation itself—no money moves, no subscriptions are created/modified, and no transactions are executed. It is purely a query/read operation.
From the tool's definition Tool name is 'listCreditPurchases' and description explicitly states it 'List[s] credit-purchase history' — a retrieval operation that queries financial transaction data without modifying or executing actions.
Attacks that exploit this kind of access
The rule that runs listCreditPurchases 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 listCreditPurchases, this is the rule to start with:
listCreditPurchases is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every listCreditPurchases call is checked against it from then on.
Questions about listCreditPurchases
List credit-purchase history for an organisation, newest first. Status, credits purchased, bonus, amount paid in AUD cents, completion timestamp. Stripe IDs stripped. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listCreditPurchases accepts 3 parameters: limit, offset, 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 listCreditPurchases: 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.
listCreditPurchases is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listCreditPurchases 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 listCreditPurchases. 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.
listCreditPurchases 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.
This server
Across the catalogue