listMembers
List members of an organisation, enriched with email + display name. Auth: org id must match the credential's organisation. Returns paginated list, default limit 50 / max 200.
This record as markdown: /tools/io-stablebaseline-sb/listmembers.md
What listMembers does on Stable Baseline
AI agents call listMembers to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
offset | number | — | |
include_invited | boolean | — | When true, include rows that haven't joined yet (joined_at IS NULL). |
organisation_id | string | Yes | Organisation UUID. Must match the credential's organisation. |
Parameters from the server's own tool schema.
Why listMembers is rated Low
This is a read-only query operation that retrieves member information (email, display name) from the organization. It has authentication guards (org id must match credentials) to prevent cross-org leakage. The blast radius of misuse is low—an agent listing members reveals organizational structure but cannot modify, delete, or trigger external actions. Proper classification: Read.
From the tool's definition Tool name 'listMembers' and description 'List members of an organisation' — retrieves/queries data with no side effects. Returns paginated list only; no modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs listMembers 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 listMembers, this is the rule to start with:
listMembers is read-only, so it stays allowed. 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 listMembers call is checked against it from then on.
Questions about listMembers
List members of an organisation, enriched with email + display name. Auth: org id must match the credential's organisation. Returns paginated list, default limit 50 / max 200. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listMembers accepts 4 parameters: limit, offset, include_invited, organisation_id. Required: 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 listMembers: 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.
listMembers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listMembers 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 listMembers. 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.
listMembers 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