getMember
Fetch a single organisation member by user_id, enriched with profile (email + display name). Auth: org id must match the credential's organisation.
This record as markdown: /tools/io-stablebaseline-sb/getmember.md
What getMember does on Stable Baseline
AI agents call getMember 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 |
|---|---|---|---|
user_id | string | Yes | User UUID of the member to fetch. |
organisation_id | string | Yes | Organisation UUID. Must match the credential's organisation. |
Parameters from the server's own tool schema.
Why getMember is rated Low
This tool retrieves user profile information (email, display name) from an organization's member records. It has no side effects, does not modify data, and the authorization check (org id must match credential's organization) limits scope. The blast radius of misuse is low—an attacker could enumerate organization members, but cannot modify data, execute commands, or cause irreversible harm.
From the tool's definition Fetch a single organisation member by user_id, enriched with profile (email + display name). The verb 'Fetch' and the read-only nature of retrieving member profile data indicates no modification or side effects.
Attacks that exploit this kind of access
The rule that runs getMember 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 getMember, this is the rule to start with:
getMember 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 getMember call is checked against it from then on.
Questions about getMember
Fetch a single organisation member by user_id, enriched with profile (email + display name). Auth: org id must match the credential's organisation. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getMember 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 getMember: 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.
getMember 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 getMember 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 getMember. 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.
getMember 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