grantTeamWorkspaceAccess
Grant a team read/write/admin access to a workspace. Idempotent. Team and workspace must be in the same organisation.
This record as markdown: /tools/io-stablebaseline-sb/grantteamworkspaceaccess.md
What grantTeamWorkspaceAccess does on Stable Baseline
AI agents use grantTeamWorkspaceAccess 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 grantTeamWorkspaceAccess is rated Medium
This tool creates or modifies access control grants, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial).
From the tool's definition Tool grants 'read/write/admin access to a workspace' — explicitly grants permissions that modify access control state. The description indicates this is an idempotent operation that changes resource sharing/access levels.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs grantTeamWorkspaceAccess 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 grantTeamWorkspaceAccess, this is the rule to start with:
grantTeamWorkspaceAccess 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 grantTeamWorkspaceAccess call is checked against it from then on.
Questions about grantTeamWorkspaceAccess
Grant a team read/write/admin access to a workspace. Idempotent. Team and workspace must be in the same organisation. 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.
grantTeamWorkspaceAccess 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 grantTeamWorkspaceAccess: 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.
grantTeamWorkspaceAccess 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 grantTeamWorkspaceAccess 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 grantTeamWorkspaceAccess. 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.
grantTeamWorkspaceAccess 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