listPlanPhases
List phases for a plan ordered by position.
This record as markdown: /tools/io-stablebaseline-sb/listplanphases.md
What listPlanPhases does on Stable Baseline
AI agents call listPlanPhases 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 |
Parameters from the server's own tool schema.
Why listPlanPhases is rated Low
This tool retrieves and queries plan phase data in read-only fashion. The verb 'list' and the passive nature of ordering existing data by position confirms this is a Read operation. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could retrieve phases it shouldn't see, but cannot alter the plan structure or trigger external operations.
From the tool's definition Tool name 'listPlanPhases' and description 'List phases for a plan ordered by position' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs listPlanPhases 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 listPlanPhases, this is the rule to start with:
listPlanPhases 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 listPlanPhases call is checked against it from then on.
Questions about listPlanPhases
List phases for a plan ordered by position. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listPlanPhases accepts 1 parameter: planId. 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 listPlanPhases: 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.
listPlanPhases 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 listPlanPhases 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 listPlanPhases. 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.
listPlanPhases 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