listProjects
List projects in a workspace. Supports query filtering by project name.
This record as markdown: /tools/io-stablebaseline-sb/listprojects.md
What listProjects does on Stable Baseline
AI agents call listProjects 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, description, workspace_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. |
workspaceId | string | Yes |
Parameters from the server's own tool schema.
Why listProjects is rated Low
This tool retrieves or queries project data with optional filtering—a classic Read operation with no side effects. The blast radius of misuse is minimal: an attacker could only enumerate projects they may already have access to in their workspace. No data is modified, deleted, or financial operations are triggered.
From the tool's definition Tool description states 'List projects in a workspace. Supports query filtering by project name.' The verb 'list' and the absence of any modification, deletion, or execution capability indicate a read-only operation.
Attacks that exploit this kind of access
The rule that runs listProjects 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 listProjects, this is the rule to start with:
listProjects 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 listProjects call is checked against it from then on.
Questions about listProjects
List projects in a workspace. Supports query filtering by project name. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listProjects accepts 8 parameters: limit, query, fields, offset, toDate, fromDate, dateField, workspaceId. Required: workspaceId. 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 listProjects: 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.
listProjects 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 listProjects 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 listProjects. 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.
listProjects 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