getOrganisation
Read a single organisation by id. Returns id, name, slug, description, settings (jsonb), created_at, member_count (active members) and plan_tier (subscription_tier). The organisation must match the calling credential's organisation. Read-only.
This record as markdown: /tools/io-stablebaseline-sb/getorganisation.md
What getOrganisation does on Stable Baseline
AI agents call getOrganisation 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 getOrganisation is rated Low
This tool retrieves organizational metadata without modifying, executing operations, or affecting data. The explicit 'Read-only' designation and query-like behavior (get by id) confirm it belongs in the Read category. Access is scoped to the calling credential's own organisation, limiting blast radius.
From the tool's definition Tool name 'getOrganisation' and description explicitly states 'Read a single organisation by id' and 'Read-only.' Returns metadata (id, name, slug, description, settings, created_at, member_count, plan_tier) with no side effects.
Attacks that exploit this kind of access
The rule that runs getOrganisation 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 getOrganisation, this is the rule to start with:
getOrganisation 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 getOrganisation call is checked against it from then on.
Questions about getOrganisation
Read a single organisation by id. Returns id, name, slug, description, settings (jsonb), created_at, member_count (active members) and plan_tier (subscription_tier). The organisation must match the calling credential's organisation. Read-only. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getOrganisation 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 getOrganisation: 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.
getOrganisation 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 getOrganisation 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 getOrganisation. 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.
getOrganisation 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