updateOrganisation
Update an organisation's name and/or description. Auth: ceiling — credential must hold can_admin_org capability AND user must be org owner/admin. Rate limit 30/min. At least one of name/description required. Returns updated row.
This record as markdown: /tools/io-stablebaseline-sb/updateorganisation.md
What updateOrganisation does on Stable Baseline
AI agents use updateOrganisation 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 |
|---|---|---|---|
name | string | — | |
description | string | null | — | |
organisation_id | string | Yes | Organisation UUID. Must equal the credential's organisation. |
Parameters from the server's own tool schema.
Why updateOrganisation is rated Medium
This tool creates or modifies data reversibly (org name and description). It does not delete, execute code, move money, or trigger external operations. The high severity reflects that updating organization metadata affects all members' context and could be misused by a compromised admin credential to confuse or redirect the entire organization, but the impact remains bounded to metadata rather than destructive or…
From the tool's definition Tool description states 'Update an organisation's name and/or description' and 'Returns updated row' — modifies organization metadata reversibly.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs updateOrganisation 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 updateOrganisation, this is the rule to start with:
updateOrganisation 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 updateOrganisation call is checked against it from then on.
Questions about updateOrganisation
Update an organisation's name and/or description. Auth: ceiling — credential must hold can_admin_org capability AND user must be org owner/admin. Rate limit 30/min. At least one of name/description required. Returns updated row. 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.
updateOrganisation accepts 3 parameters: name, description, 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 updateOrganisation: 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.
updateOrganisation 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 updateOrganisation 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 updateOrganisation. 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.
updateOrganisation 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