addTeamMember
Add a user to a team as a regular member. Idempotent — returns already_member=true if already on the team. User must be an active organisation member.
This record as markdown: /tools/io-stablebaseline-sb/addteammember.md
What addTeamMember does on Stable Baseline
AI agents use addTeamMember 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 | |
user_id | string | Yes |
Parameters from the server's own tool schema.
Why addTeamMember is rated Medium
This tool creates or modifies team membership state, which is a Write-category operation. Severity is medium because misuse could grant unauthorized access to team resources and information, but the blast radius is limited to team-scope impacts (not organization-wide or financial). The idempotency note confirms the operation is reversible and side-effect-bounded.
From the tool's definition Tool description states 'Add a user to a team as a regular member' — a create/modify operation that grants team membership. This is reversible (members can be removed later) and does not move money, execute code, or delete data.
Attacks that exploit this kind of access
The rule that runs addTeamMember 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 addTeamMember, this is the rule to start with:
addTeamMember 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 addTeamMember call is checked against it from then on.
Questions about addTeamMember
Add a user to a team as a regular member. Idempotent — returns already_member=true if already on the team. User must be an active organisation member. 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.
addTeamMember accepts 2 parameters: team_id, user_id. Required: team_id, user_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 addTeamMember: 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.
addTeamMember 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 addTeamMember 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 addTeamMember. 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.
addTeamMember 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