removeMember
Hard-remove a member from an organisation, cascading to workspace and team memberships and resource permissions. Refuses self-removal and last-owner removal. The paid seat count is NOT changed here: use previewSubscriptionChange and then applySubscriptionChange for a seat change. Rate limit 5/min...
This record as markdown: /tools/io-stablebaseline-sb/removemember.md
What removeMember does on Stable Baseline
AI agents call removeMember 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 |
|---|---|---|---|
user_id | string | Yes | |
organisation_id | string | Yes |
Parameters from the server's own tool schema.
Why removeMember is rated Critical
An AI agent that decides to call removeMember doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Stable Baseline is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs removeMember 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 removeMember, this is the rule to start with:
removeMember 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 removeMember call is checked against it from then on.
Questions about removeMember
Hard-remove a member from an organisation, cascading to workspace and team memberships and resource permissions. Refuses self-removal and last-owner removal. The paid seat count is NOT changed here: use previewSubscriptionChange and then applySubscriptionChange for a seat change. Rate limit 5/min. Use when the user asks to remove, kick out, fire, offboard, or fully terminate a member's access to the organisation. 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.
removeMember accepts 2 parameters: user_id, organisation_id. Required: user_id, 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 removeMember: 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.
removeMember 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 removeMember 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 removeMember. 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.
removeMember 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