getFolderHierarchy
Get the folder and document tree starting from a specific folder. Alias for getProjectHierarchy with folderId.
This record as markdown: /tools/io-stablebaseline-sb/getfolderhierarchy.md
What getFolderHierarchy does on Stable Baseline
AI agents call getFolderHierarchy 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 |
|---|---|---|---|
query | string | — | Filter by name/title (case-insensitive). |
toDate | string | — | ISO 8601 date filter (to). |
folderId | string | Yes | The folder ID to start from. |
fromDate | string | — | ISO 8601 date filter (from). |
maxDepth | number | — | Max nesting depth. Default: 10, max: 20. |
dateField | string | — | Date field to filter. Default: updated_at. |
includeDocuments | boolean | — | Include documents. Default: true. |
Parameters from the server's own tool schema.
Why getFolderHierarchy is rated Low
This tool retrieves hierarchical structural information (folders and documents) from a workspace. It performs a query with no ability to modify, delete, or execute operations. The blast radius of misuse is minimal — an agent could over-query or access unintended folder structures, but cannot alter data or trigger external actions.
From the tool's definition Tool description explicitly states 'Get the folder and document tree' — a retrieval operation with no side effects. The verb 'Get' and absence of any modification language confirm this is a read-only query.
Attacks that exploit this kind of access
The rule that runs getFolderHierarchy 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 getFolderHierarchy, this is the rule to start with:
getFolderHierarchy 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 getFolderHierarchy call is checked against it from then on.
Questions about getFolderHierarchy
Get the folder and document tree starting from a specific folder. Alias for getProjectHierarchy with folderId. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getFolderHierarchy accepts 7 parameters: query, toDate, folderId, fromDate, maxDepth, dateField, includeDocuments. Required: folderId. 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 getFolderHierarchy: 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.
getFolderHierarchy 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 getFolderHierarchy 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 getFolderHierarchy. 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.
getFolderHierarchy 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