createTeam
Create a new team inside an organisation. Caller is added as the team's lead. Subject to plan team limit. Rate limit 30/min.
This record as markdown: /tools/io-stablebaseline-sb/createteam.md
What createTeam does on Stable Baseline
AI agents use createTeam 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 | |
color | string | — | Optional 6-digit hex colour. Defaults to #6366f1. |
description | string | — | |
organisation_id | string | Yes |
Parameters from the server's own tool schema.
Why createTeam is rated Medium
This tool creates new persistent entities (teams) in the system, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move money. However, it can impact organizational structure and may trigger cascading effects based on sibling tools like 'applyTaskDependencyCascade' and plan limits.
From the tool's definition Tool description states 'Create a new team inside an organisation' and 'Caller is added as the team's lead.' The word 'Create' directly indicates a write operation that modifies organizational structure.
Attacks that exploit this kind of access
The rule that runs createTeam 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 createTeam, this is the rule to start with:
createTeam 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 createTeam call is checked against it from then on.
Questions about createTeam
Create a new team inside an organisation. Caller is added as the team's lead. Subject to plan team limit. Rate limit 30/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.
createTeam accepts 4 parameters: name, color, description, organisation_id. Required: name, organisation_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 createTeam: 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.
createTeam 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 createTeam 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 createTeam. 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.
createTeam 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