createWorkspace
Create a new workspace inside the organisation. Auth: ceiling — credential must hold can_lifecycle AND user must be org owner/admin. Rate limit 30/min. Slug auto-generated. Caller becomes workspace owner. Plan limits surface as WORKSPACE_LIMIT_REACHED errors.
This record as markdown: /tools/io-stablebaseline-sb/createworkspace.md
What createWorkspace does on Stable Baseline
AI agents use createWorkspace 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 | |
organisation_id | string | Yes | Organisation UUID. Must equal the credential's organisation. |
Parameters from the server's own tool schema.
Why createWorkspace is rated Medium
This tool creates a new persistent organizational resource (workspace) with structural implications—the caller gains ownership rights and the action is reversible but consequential. It does not delete or execute arbitrary code (ruling out Destructive/Execute), nor does it move money (ruling out Financial). It modifies organizational structure by adding a new entity, making it Write.
From the tool's definition Creates a new workspace inside the organisation; caller becomes workspace owner. Auth requires `can_lifecycle` credential and org owner/admin role. Rate limited to 30/min. Plan limits enforced.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs createWorkspace 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 createWorkspace, this is the rule to start with:
createWorkspace 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 createWorkspace call is checked against it from then on.
Questions about createWorkspace
Create a new workspace inside the organisation. Auth: ceiling — credential must hold can_lifecycle AND user must be org owner/admin. Rate limit 30/min. Slug auto-generated. Caller becomes workspace owner. Plan limits surface as WORKSPACE_LIMIT_REACHED errors. 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.
createWorkspace accepts 2 parameters: name, organisation_id. Required: name, 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 createWorkspace: 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.
createWorkspace 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 createWorkspace 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 createWorkspace. 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.
createWorkspace 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