getOrgSettings
Read an organisation's settings JSON and the derived enabled-features map (plans, documents, improvements, compliance, knowledge_graph: all booleans). Also ai: the kind of work the assistant and the organisation's agents run on (everyday or thinking) and whether each runs on the organisation's ow...
This record as markdown: /tools/io-stablebaseline-sb/getorgsettings.md
What getOrgSettings does on Stable Baseline
AI agents call getOrgSettings 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 getOrgSettings is rated Low
Even though getOrgSettings only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs getOrgSettings 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 getOrgSettings, this is the rule to start with:
getOrgSettings 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 getOrgSettings call is checked against it from then on.
Questions about getOrgSettings
Read an organisation's settings JSON and the derived enabled-features map (plans, documents, improvements, compliance, knowledge_graph: all booleans). Also ai: the kind of work the assistant and the organisation's agents run on (everyday or thinking) and whether each runs on the organisation's own AI, on Stable Baseline's AI, or is stopped until an owner or admin fixes it (Organisation settings, AI). 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.
getOrgSettings 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 getOrgSettings: 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.
getOrgSettings 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 getOrgSettings 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 getOrgSettings. 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.
getOrgSettings 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