listWorkspaces
List workspaces you have access to. Supports query filtering by name/slug.
This record as markdown: /tools/io-stablebaseline-sb/listworkspaces.md
What listWorkspaces does on Stable Baseline
AI agents call listWorkspaces 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 | — | |
query | string | — | |
fields | array | — | Field projection. Valid fields: id, name, slug, organization_id, created_at, updated_at. |
offset | number | — | |
toDate | string | — | ISO 8601 date filter (to). |
fromDate | string | — | ISO 8601 date filter (from). |
dateField | string | — | Date field to filter. Default: updated_at. |
Parameters from the server's own tool schema.
Why listWorkspaces is rated Low
This tool queries and returns a list of workspaces filtered by name or slug parameters. It is a read-only operation that retrieves information without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an agent could enumerate workspaces but cannot modify or destroy data or trigger external operations.
From the tool's definition Tool name 'listWorkspaces' and description 'List workspaces you have access to. Supports query filtering by name/slug' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs listWorkspaces 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 listWorkspaces, this is the rule to start with:
listWorkspaces 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 listWorkspaces call is checked against it from then on.
Questions about listWorkspaces
List workspaces you have access to. Supports query filtering by name/slug. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listWorkspaces accepts 7 parameters: limit, query, fields, offset, toDate, fromDate, dateField. 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 listWorkspaces: 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.
listWorkspaces 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 listWorkspaces 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 listWorkspaces. 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.
listWorkspaces 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