getPlanHierarchy
Get the complete plan hierarchy (phases, tasks, improvements) in one call. Recommended first call for plan navigation.
This record as markdown: /tools/io-stablebaseline-sb/getplanhierarchy.md
What getPlanHierarchy does on Stable Baseline
AI agents call getPlanHierarchy 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 |
|---|---|---|---|
planId | string | Yes | Accepts either the UUID or the friendly id (e.g. PLN-3); friendly ids are resolved within your organisation. |
projectId | string | — | Optional. Narrows a friendly-id lookup to one project. Only needed when a friendly id is ambiguous — TAS-/IMP-/PLN- ids are numbered per PROJECT, so the same id |
Parameters from the server's own tool schema.
Why getPlanHierarchy is rated Low
This tool queries and retrieves existing plan data (phases, tasks, improvements) without modifying, deleting, or executing operations. It is a straightforward data retrieval endpoint with no blast radius beyond information disclosure.
From the tool's definition Tool description states 'Get the complete plan hierarchy' — a retrieval operation with no side effects. The verb 'Get' and context of 'plan navigation' indicate read-only access to hierarchical data structures.
Attacks that exploit this kind of access
The rule that runs getPlanHierarchy 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 getPlanHierarchy, this is the rule to start with:
getPlanHierarchy 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 getPlanHierarchy call is checked against it from then on.
Questions about getPlanHierarchy
Get the complete plan hierarchy (phases, tasks, improvements) in one call. Recommended first call for plan navigation. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
getPlanHierarchy accepts 2 parameters: planId, projectId. Required: planId. 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 getPlanHierarchy: 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.
getPlanHierarchy 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 getPlanHierarchy 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 getPlanHierarchy. 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.
getPlanHierarchy 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