createOrganisation
Create a new organisation owned by the calling credential's user. Auth: server-side eligibility gate via can_user_create_organization (free-tier users may only have one org). Per-credential rate limit 3/day. Slug auto-generated. The new org is OUTSIDE the credential's current scope (credentials a...
This record as markdown: /tools/io-stablebaseline-sb/createorganisation.md
What createOrganisation does on Stable Baseline
AI agents use createOrganisation 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 | Yes | Display name. |
description | string | — | Optional free-text description. |
Parameters from the server's own tool schema.
Why createOrganisation is rated Medium
This tool creates new data (a new organisation) but the action is reversible—organisations can typically be deleted or archived in most systems. It is not a deletion, not code execution, not financial, and not a direct read.
From the tool's definition Creates a new organisation owned by the calling credential's user. Auth: server-side eligibility gate via `can_user_create_organization` (free-tier users may only have one org). Rate limit 3/day. The new org is OUTSIDE the credential's current scope.
Attacks that exploit this kind of access
The rule that runs createOrganisation 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 createOrganisation, this is the rule to start with:
createOrganisation 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 createOrganisation call is checked against it from then on.
Questions about createOrganisation
Create a new organisation owned by the calling credential's user. Auth: server-side eligibility gate via can_user_create_organization (free-tier users may only have one org). Per-credential rate limit 3/day. Slug auto-generated. The new org is OUTSIDE the credential's current scope (credentials are bound to one org); to use the new org from MCP, mint a fresh credential. 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.
createOrganisation accepts 2 parameters: name, description. Required: name. 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 createOrganisation: 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.
createOrganisation 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 createOrganisation 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 createOrganisation. 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.
createOrganisation 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