listTeams
List teams in an organization, with optional search filter and an includeMembers flag that fans out to v_team_members in a single round-trip. Supply EITHER organizationId OR workspaceId (the workspace's parent org is resolved automatically). Use this when the user asks about teams generically (e....
This record as markdown: /tools/io-stablebaseline-sb/listteams.md
What listTeams does on Stable Baseline
AI agents call listTeams 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 |
|---|---|---|---|
q | string | — | Optional ILIKE search on team name/slug. |
limit | number | — | Max teams per page (1-200, default 50). |
offset | number | — | Pagination offset. |
workspaceId | string | — | Workspace UUID. The parent organization is resolved from v_workspaces. |
includeMembers | boolean | — | When true, each team gets a `members` array (user_id, role, joined_at). Capped at 500 total members across the page. Default false. |
organizationId | string | — | Organization UUID. Either this OR workspaceId is required. |
Parameters from the server's own tool schema.
Why listTeams is rated Low
This tool performs a straightforward data retrieval operation with no side effects. It queries team information from a knowledge management system and returns results. The explicit 'Read-only' label and absence of any create, update, delete, or execution capabilities confirm it belongs in the Read category with low severity.
From the tool's definition Tool description explicitly states 'Read-only' and the action is to 'List teams in an organization' with optional search and member expansion. It retrieves data (teams and optionally their members) without modifying anything.
Attacks that exploit this kind of access
The rule that runs listTeams 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 listTeams, this is the rule to start with:
listTeams 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 listTeams call is checked against it from then on.
Questions about listTeams
List teams in an organization, with optional search filter and an includeMembers flag that fans out to v_team_members in a single round-trip. Supply EITHER organizationId OR workspaceId (the workspace's parent org is resolved automatically). Use this when the user asks about teams generically (e.g. 'show me my teams') or before assigning a team via updateImprovement(owner_team_id=…). Read-only. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listTeams accepts 6 parameters: q, limit, offset, workspaceId, includeMembers, organizationId. 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 listTeams: 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.
listTeams 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 listTeams 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 listTeams. 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.
listTeams 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