getTeam
Get a single team by ID with profile-enriched member list (display_name, email, avatar_url, role, joined_at). Set includeMembers=false to skip the member fan-out and just return team metadata. Read-only.
This record as markdown: /tools/io-stablebaseline-sb/getteam.md
What getTeam does on Stable Baseline
AI agents call getTeam 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 |
|---|---|---|---|
teamId | string | Yes | Team UUID. |
includeMembers | boolean | — | Include the team's members enriched with user profile info. Default true. |
Parameters from the server's own tool schema.
Why getTeam is rated Low
This is a straightforward data retrieval operation. It queries team information and optionally member details with no capability to create, modify, delete, or execute any actions.
From the tool's definition Tool description explicitly states 'Get a single team by ID' and 'Read-only.' Returns team metadata and member profile information (display_name, email, avatar_url, role, joined_at) without modification options.
Attacks that exploit this kind of access
The rule that runs getTeam 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 getTeam, this is the rule to start with:
getTeam 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 getTeam call is checked against it from then on.
Questions about getTeam
Get a single team by ID with profile-enriched member list (display_name, email, avatar_url, role, joined_at). Set includeMembers=false to skip the member fan-out and just return team metadata. Read-only. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getTeam accepts 2 parameters: teamId, includeMembers. Required: teamId. 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 getTeam: 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.
getTeam 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 getTeam 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 getTeam. 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.
getTeam 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