getProjectHierarchy
Get the complete folder and document tree for a project in one call. Recommended first call for navigation.
This record as markdown: /tools/io-stablebaseline-sb/getprojecthierarchy.md
What getProjectHierarchy does on Stable Baseline
AI agents call getProjectHierarchy 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 | — | Start from this folder instead of project root. |
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. |
projectId | string | — | Project ID. Required if folderId not provided. |
includeDocuments | boolean | — | Include documents. Default: true. |
Parameters from the server's own tool schema.
Why getProjectHierarchy is rated Low
This tool retrieves and queries the hierarchical structure of project documents and folders. It performs no modifications, deletions, or external operations—it simply fetches and returns data for navigation purposes. This is a read-only operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'getProjectHierarchy' and description 'Get the complete folder and document tree for a project in one call' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs getProjectHierarchy 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 getProjectHierarchy, this is the rule to start with:
getProjectHierarchy 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 getProjectHierarchy call is checked against it from then on.
Questions about getProjectHierarchy
Get the complete folder and document tree for a project in one call. Recommended first call for navigation. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getProjectHierarchy accepts 8 parameters: query, toDate, folderId, fromDate, maxDepth, dateField, projectId, includeDocuments. 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 getProjectHierarchy: 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.
getProjectHierarchy 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 getProjectHierarchy 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 getProjectHierarchy. 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.
getProjectHierarchy 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