listFolders
List folders in a project. Use parentId for nested folders. For full tree, use getProjectHierarchy instead.
This record as markdown: /tools/io-stablebaseline-sb/listfolders.md
What listFolders does on Stable Baseline
AI agents call listFolders 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, projectId, parentId, name, position, createdAt, updatedAt. |
offset | number | — | |
toDate | string | — | ISO 8601 date filter (to). |
fromDate | string | — | ISO 8601 date filter (from). |
parentId | string | — | |
dateField | string | — | Date field to filter. Default: updated_at. |
projectId | string | Yes |
Parameters from the server's own tool schema.
Why listFolders is rated Low
This tool retrieves and queries folder structure data with no side effects. It is a pure read operation that lists existing project folders. The low severity reflects minimal blast radius—an AI agent misusing this would at worst retrieve unwanted folder metadata, with no destructive or financial impact. High confidence due to clear read-only semantics in both name and description.
From the tool's definition Tool name is 'listFolders' and description states it 'List folders in a project' with optional parentId parameter for navigation. No modification, deletion, or execution capability described.
Attacks that exploit this kind of access
The rule that runs listFolders 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 listFolders, this is the rule to start with:
listFolders 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 listFolders call is checked against it from then on.
Questions about listFolders
List folders in a project. Use parentId for nested folders. For full tree, use getProjectHierarchy instead. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listFolders accepts 9 parameters: limit, query, fields, offset, toDate, fromDate, parentId, dateField, projectId. Required: projectId. 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 listFolders: 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.
listFolders 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 listFolders 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 listFolders. 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.
listFolders 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