reorderPlanPhases
Reorder plan phases by setting position values. WBS codes are recalculated.
This record as markdown: /tools/io-stablebaseline-sb/reorderplanphases.md
What reorderPlanPhases does on Stable Baseline
AI agents use reorderPlanPhases to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
items | array | Yes | Array of {phaseId, position}. |
Parameters from the server's own tool schema.
Why reorderPlanPhases is rated Medium
This tool creates or modifies plan data (phase ordering and WBS codes) in a reversible manner. Reordering is not destructive since the phases themselves are preserved—only their sequence and codes change. It could impact downstream dependencies or reports that rely on phase order, but the action is reversible (can be reordered again).
From the tool's definition Tool name 'reorderPlanPhases' and description 'Reorder plan phases by setting position values. WBS codes are recalculated.' indicate modification of plan structure. The recalculation of WBS codes suggests systematic updates to hierarchical data.
Attacks that exploit this kind of access
The rule that runs reorderPlanPhases 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 reorderPlanPhases, this is the rule to start with:
reorderPlanPhases stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 reorderPlanPhases call is checked against it from then on.
Questions about reorderPlanPhases
Reorder plan phases by setting position values. WBS codes are recalculated. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
reorderPlanPhases accepts 1 parameter: items. Required: items. 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 reorderPlanPhases: 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.
reorderPlanPhases is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reorderPlanPhases 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 reorderPlanPhases. 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.
reorderPlanPhases 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