updateTeamWorkspaceAccess
Update an existing team's workspace access level. Refuses if no grant exists — call grantTeamWorkspaceAccess first. No-op when level matches.
This record as markdown: /tools/io-stablebaseline-sb/updateteamworkspaceaccess.md
What updateTeamWorkspaceAccess does on Stable Baseline
AI agents use updateTeamWorkspaceAccess 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 |
|---|---|---|---|
team_id | string | Yes | |
workspace_id | string | Yes | |
permission_level | string | Yes |
Parameters from the server's own tool schema.
Why updateTeamWorkspaceAccess is rated Medium
This tool creates or modifies access control settings for teams in a workspace. While it does not delete data (hence not Destructive), changing team workspace access levels is a reversible modification that affects who can interact with organizational resources.
From the tool's definition Tool description states 'Update an existing team's workspace access level' — directly modifies access permissions. Name contains 'update', a Write operation verb.
Attacks that exploit this kind of access
The rule that runs updateTeamWorkspaceAccess 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 updateTeamWorkspaceAccess, this is the rule to start with:
updateTeamWorkspaceAccess 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 updateTeamWorkspaceAccess call is checked against it from then on.
Questions about updateTeamWorkspaceAccess
Update an existing team's workspace access level. Refuses if no grant exists — call grantTeamWorkspaceAccess first. No-op when level matches. 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.
updateTeamWorkspaceAccess accepts 3 parameters: team_id, workspace_id, permission_level. Required: team_id, workspace_id, permission_level. 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 updateTeamWorkspaceAccess: 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.
updateTeamWorkspaceAccess 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 updateTeamWorkspaceAccess 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 updateTeamWorkspaceAccess. 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.
updateTeamWorkspaceAccess 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