updateWorkspaceMember
Change an existing workspace member's role. Caller must be a workspace owner or admin. Cannot self-demote from owner/admin to editor/viewer — transfer the role first.
This record as markdown: /tools/io-stablebaseline-sb/updateworkspacemember.md
What updateWorkspaceMember does on Stable Baseline
AI agents use updateWorkspaceMember 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 |
|---|---|---|---|
user_id | string | Yes | |
workspace_id | string | Yes | |
workspace_role | string | Yes |
Parameters from the server's own tool schema.
Why updateWorkspaceMember is rated Medium
This tool modifies user access levels within a workspace. While reversible (roles can be changed back), it has significant blast radius: a compromised agent could alter permissions for team members, potentially escalating privileges, revoking access, or creating security gaps. The context of 'company brain' containing sensitive docs, diagrams, and knowledge graphs amplifies the risk.
From the tool's definition Tool description states 'Change an existing workspace member's role', which is a direct modification operation.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs updateWorkspaceMember 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 updateWorkspaceMember, this is the rule to start with:
updateWorkspaceMember 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 updateWorkspaceMember call is checked against it from then on.
Questions about updateWorkspaceMember
Change an existing workspace member's role. Caller must be a workspace owner or admin. Cannot self-demote from owner/admin to editor/viewer — transfer the role first. 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.
updateWorkspaceMember accepts 3 parameters: user_id, workspace_id, workspace_role. Required: user_id, workspace_id, workspace_role. 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 updateWorkspaceMember: 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.
updateWorkspaceMember 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 updateWorkspaceMember 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 updateWorkspaceMember. 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.
updateWorkspaceMember 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