getCreditPackages
List active credit packages available for purchase (name, credits, bonus_credits, price in cents AUD). Catalog read — visible to any MCP credential. Pair with createCreditPurchaseLink (Phase 6) to start a checkout.
This record as markdown: /tools/io-stablebaseline-sb/getcreditpackages.md
What getCreditPackages does on Stable Baseline
AI agents call getCreditPackages 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.
Why getCreditPackages is rated Low
This is a straightforward catalog listing operation. While it relates to financial products (credit packages with pricing), the tool itself only reads and displays available options; it does not process payments, commit transactions, or modify financial state. The description explicitly notes 'Catalog read' and indicates that checkout is handled separately by a paired tool (createCreditPurchaseLink).
From the tool's definition The tool 'getCreditPackages' is described as 'List active credit packages available for purchase (name, credits, bonus_credits, price in cents AUD).
Attacks that exploit this kind of access
The rule that runs getCreditPackages 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 getCreditPackages, this is the rule to start with:
getCreditPackages 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 getCreditPackages call is checked against it from then on.
Questions about getCreditPackages
List active credit packages available for purchase (name, credits, bonus_credits, price in cents AUD). Catalog read — visible to any MCP credential. Pair with createCreditPurchaseLink (Phase 6) to start a checkout. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for getCreditPackages: 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.
getCreditPackages 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 getCreditPackages 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 getCreditPackages. 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.
getCreditPackages 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