setMemberActive
Soft-deactivate or reactivate an organisation member. Refuses self-deactivation, last-admin/owner deactivation, and deactivation of an owner. Rate limit 30/min. Use when the user asks to deactivate, suspend, freeze, reactivate, or unfreeze a member without fully removing them.
This record as markdown: /tools/io-stablebaseline-sb/setmemberactive.md
What setMemberActive does on Stable Baseline
AI agents use setMemberActive 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 |
|---|---|---|---|
user_id | string | Yes | |
is_active | boolean | Yes | |
organisation_id | string | Yes |
Parameters from the server's own tool schema.
Why setMemberActive is rated Medium
This tool modifies organisational access and member status in a reversible way (deactivate/reactivate). It does not delete data or cause irreversible harm, so it is Write rather than Destructive. However, it affects member privileges and organisational structure, which could disrupt operations or lock out users if misused by an agent; hence severity is high rather than medium.
From the tool's definition Tool description states 'Soft-deactivate or reactivate an organisation member' — this reversibly modifies member status without permanent deletion.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs setMemberActive 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 setMemberActive, this is the rule to start with:
setMemberActive 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 setMemberActive call is checked against it from then on.
Questions about setMemberActive
Soft-deactivate or reactivate an organisation member. Refuses self-deactivation, last-admin/owner deactivation, and deactivation of an owner. Rate limit 30/min. Use when the user asks to deactivate, suspend, freeze, reactivate, or unfreeze a member without fully removing them. 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.
setMemberActive accepts 3 parameters: user_id, is_active, organisation_id. Required: user_id, is_active, 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 setMemberActive: 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.
setMemberActive 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 setMemberActive 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 setMemberActive. 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.
setMemberActive 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