updateOrgSettings
Update an organisation's settings object via deep merge. Auth: ceiling — credential must hold can_admin_org AND user must be org owner/admin. Rate limit 30/min. Patches that touch enabledFeatures are rejected — use updateOrgFeatureFlags instead. Settings that Stable Baseline sets for the organisa...
This record as markdown: /tools/io-stablebaseline-sb/updateorgsettings.md
What updateOrgSettings does on Stable Baseline
AI agents use updateOrgSettings to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
settings | object | Yes | The patch: top-level keys are deep-merged with the existing settings; null removes a key. enabledFeatures is rejected; availableFeatures and plan limit override |
organisation_id | string | Yes |
Parameters from the server's own tool schema.
Why updateOrgSettings is rated Medium
An AI agent can call updateOrgSettings faster than any human can review: one bad instruction and it creates or modifies resources in Stable Baseline by the hundred, each call as confident as the last.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs updateOrgSettings 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 updateOrgSettings, this is the rule to start with:
updateOrgSettings stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 updateOrgSettings call is checked against it from then on.
Questions about updateOrgSettings
Update an organisation's settings object via deep merge. Auth: ceiling — credential must hold can_admin_org AND user must be org owner/admin. Rate limit 30/min. Patches that touch enabledFeatures are rejected — use updateOrgFeatureFlags instead. Settings that Stable Baseline sets for the organisation are refused: availableFeatures (which features are available to it) and any plan limit override (a key whose name contains override). It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
updateOrgSettings accepts 2 parameters: settings, organisation_id. Required: settings, 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 updateOrgSettings: 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.
updateOrgSettings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the updateOrgSettings 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 updateOrgSettings. 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.
updateOrgSettings 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