getCurrentPlanEntitlements
Read the plan entitlements (limits + capability flags) that apply to the caller's organisation. Returns { tier, display_name, limits, features }. The Enterprise row is filtered for non-admin callers by the underlying view. Read-only.
This record as markdown: /tools/io-stablebaseline-sb/getcurrentplanentitlements.md
What getCurrentPlanEntitlements does on Stable Baseline
AI agents call getCurrentPlanEntitlements 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 | Organisation UUID. Must equal the credential's organisation. |
Parameters from the server's own tool schema.
Why getCurrentPlanEntitlements is rated Low
This tool retrieves configuration and entitlement data for the caller's organization without any side effects, data modification, or irreversible actions. The read-only nature and focus on querying plan information clearly fits the Read category. Severity is low because entitlement data is non-sensitive organizational metadata that reflects what the user already knows about their subscription.
From the tool's definition Tool description explicitly states 'Read-only' and 'Read the plan entitlements'. Returns organizational tier, display name, limits, and features without modification.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs getCurrentPlanEntitlements 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 getCurrentPlanEntitlements, this is the rule to start with:
getCurrentPlanEntitlements 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 getCurrentPlanEntitlements call is checked against it from then on.
Questions about getCurrentPlanEntitlements
Read the plan entitlements (limits + capability flags) that apply to the caller's organisation. Returns { tier, display_name, limits, features }. The Enterprise row is filtered for non-admin callers by the underlying view. Read-only. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getCurrentPlanEntitlements 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 getCurrentPlanEntitlements: 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.
getCurrentPlanEntitlements 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 getCurrentPlanEntitlements 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 getCurrentPlanEntitlements. 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.
getCurrentPlanEntitlements 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