updateTeam
Update a team's name, description, and/or colour. At least one field required. Slug is intentionally not editable. Rate limit 60/min.
This record as markdown: /tools/io-stablebaseline-sb/updateteam.md
What updateTeam does on Stable Baseline
AI agents use updateTeam 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 | — | |
color | string | — | |
team_id | string | Yes | |
description | string | null | — |
Parameters from the server's own tool schema.
Why updateTeam is rated Medium
This tool modifies team metadata (name, description, color) but does not delete, execute code, access financial data, or trigger irreversible changes. The changes are reversible — a team's properties can be updated again. The blast radius is moderate: incorrect team naming/description could cause organizational confusion, but the impact is limited to team metadata and can be corrected.
From the tool's definition Tool description states 'Update a team's name, description, and/or colour' — the verb 'Update' combined with modifiable fields (name, description, color) indicates reversible data modification.
Attacks that exploit this kind of access
The rule that runs updateTeam 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 updateTeam, this is the rule to start with:
updateTeam 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 updateTeam call is checked against it from then on.
Questions about updateTeam
Update a team's name, description, and/or colour. At least one field required. Slug is intentionally not editable. 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.
updateTeam accepts 4 parameters: name, color, team_id, description. Required: team_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 updateTeam: 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.
updateTeam 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 updateTeam 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 updateTeam. 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.
updateTeam 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