removeTeamMember
Remove a user from a team. Idempotent — returns removed=false if not on the team.
This record as markdown: /tools/io-stablebaseline-sb/removeteammember.md
What removeTeamMember does on Stable Baseline
AI agents call removeTeamMember to permanently remove resources in Stable Baseline, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
team_id | string | Yes | |
user_id | string | Yes |
Parameters from the server's own tool schema.
Why removeTeamMember is rated Critical
Removing a team member is a destructive action that revokes access and membership. While the operation is described as idempotent (safe to call multiple times), the act of removing a user from a team is not easily reversible without re-adding them manually, and it can affect collaboration, permissions, and access to resources.
From the tool's definition 'Remove a user from a team' — the tool explicitly removes a member from a team, which is a deletion of a membership relationship.
Attacks that exploit this kind of access
The rule that runs removeTeamMember 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 removeTeamMember, this is the rule to start with:
removeTeamMember is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every removeTeamMember call is checked against it from then on.
Questions about removeTeamMember
Remove a user from a team. Idempotent — returns removed=false if not on the team. It is categorised as a Destructive tool in the Stable Baseline MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
removeTeamMember 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 removeTeamMember: 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.
removeTeamMember is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the removeTeamMember 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 removeTeamMember. 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.
removeTeamMember 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.
Across the catalogue