getSubscription
Read the subscription state for an organisation. Returns tier, status, current billing period, seat count, member count, cancellation flag, trial end. Stripe IDs are stripped. Pair with listPaymentMethods/listInvoices for the full billing dashboard. Use when the user asks 'what plan am I on', 'ho...
This record as markdown: /tools/io-stablebaseline-sb/getsubscription.md
What getSubscription does on Stable Baseline
AI agents call getSubscription 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 getSubscription is rated Low
This tool retrieves subscription and billing metadata without modifying any data. While categorized as Read, severity is elevated to medium rather than low because subscription state information is sensitive business data that could inform attackers about organization size, billing cycles, and financial commitment.
From the tool's definition Tool description states 'Read the subscription state for an organisation' and 'Returns tier, status, current billing period, seat count, member count, cancellation flag, trial end.' These are all read-only queries with no modification capability.
Attacks that exploit this kind of access
The rule that runs getSubscription 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 getSubscription, this is the rule to start with:
getSubscription 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 getSubscription call is checked against it from then on.
Questions about getSubscription
Read the subscription state for an organisation. Returns tier, status, current billing period, seat count, member count, cancellation flag, trial end. Stripe IDs are stripped. Pair with listPaymentMethods/listInvoices for the full billing dashboard. Use when the user asks 'what plan am I on', 'how many seats do I have', 'when does my subscription renew', or to check current billing status. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getSubscription 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 getSubscription: 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.
getSubscription 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 getSubscription 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 getSubscription. 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.
getSubscription 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