getCreditBalance
Composite credit balance for an organisation: plan_credits (recurring monthly bucket), top_up_credits (purchased one-offs, gross), bonus_credits (admin grants), total, and period_end (next plan reset).
This record as markdown: /tools/io-stablebaseline-sb/getcreditbalance.md
What getCreditBalance does on Stable Baseline
AI agents call getCreditBalance 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 |
|---|---|---|---|
organisation_id | string | Yes | UUID of the organisation. Must match the credential's organisation. |
Parameters from the server's own tool schema.
Why getCreditBalance is rated Low
This is fundamentally a Read operation—it queries and returns financial account information. However, severity is elevated to 'medium' rather than 'low' because the data returned pertains to organizational financial/credit status; misuse could enable an AI agent to make informed financial decisions (e.g., deciding whether to spend credits) based on potentially unauthorized balance queries.
From the tool's definition Tool retrieves composite credit balance data (plan_credits, top_up_credits, bonus_credits, total, period_end) without modifying any underlying state. The verb 'get' and description language indicates a read-only query operation.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs getCreditBalance 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 getCreditBalance, this is the rule to start with:
getCreditBalance 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 getCreditBalance call is checked against it from then on.
Questions about getCreditBalance
Composite credit balance for an organisation: plan_credits (recurring monthly bucket), top_up_credits (purchased one-offs, gross), bonus_credits (admin grants), total, and period_end (next plan reset). It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getCreditBalance 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 getCreditBalance: 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.
getCreditBalance 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 getCreditBalance 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 getCreditBalance. 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.
getCreditBalance 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