updateWorkspace
Update a workspace's name. Auth: standard workspace-write ladder + user must be workspace owner or admin. Slug is intentionally not editable (URL-embedded). Rate limit 60/min.
This record as markdown: /tools/io-stablebaseline-sb/updateworkspace.md
What updateWorkspace does on Stable Baseline
AI agents use updateWorkspace 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 | |
workspace_id | string | Yes | Workspace UUID. |
Parameters from the server's own tool schema.
Why updateWorkspace is rated Medium
This tool creates or modifies data (workspace metadata) in a reversible manner. Renaming a workspace does not delete data, trigger external code execution, move money, or cause permanent damage. It is a standard Write operation. Severity is medium because renaming a workspace could cause confusion or organizational disruption if misused by a compromised agent, but the change is easily reverted by an authorized user.
From the tool's definition Tool description states 'Update a workspace's name' — a reversible modification operation. Authorization requires 'workspace-write' permission and workspace owner/admin role.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs updateWorkspace 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 updateWorkspace, this is the rule to start with:
updateWorkspace 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 updateWorkspace call is checked against it from then on.
Questions about updateWorkspace
Update a workspace's name. Auth: standard workspace-write ladder + user must be workspace owner or admin. Slug is intentionally not editable (URL-embedded). Rate limit 60/min. 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.
updateWorkspace accepts 2 parameters: name, workspace_id. Required: name, workspace_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 updateWorkspace: 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.
updateWorkspace 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 updateWorkspace 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 updateWorkspace. 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.
updateWorkspace 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