createPlanPhase
Create a phase in a plan. Position and wbs_code are auto-computed.
This record as markdown: /tools/io-stablebaseline-sb/createplanphase.md
What createPlanPhase does on Stable Baseline
AI agents use createPlanPhase 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 |
|---|---|---|---|
name | string | Yes | |
color | string | — | Phase color. Must be one of: #3b82f6 (Blue), #f59e0b (Amber), #8b5cf6 (Purple), #ec4899 (Pink), #06b6d4 (Cyan), #14b8a6 (Teal), #6366f1 (Indigo), #6b7280 (Gray) |
planId | string | Yes | |
status | string | — | Status: not_started, in_progress, completed, on_hold, cancelled. Default: not_started. |
end_date | string | — | YYYY-MM-DD. |
position | number | — | Position. Auto-computed if omitted. |
priority | string | — | Priority. Default: medium. |
wbs_code | string | — | WBS code. Auto-computed if omitted. |
start_date | string | — | YYYY-MM-DD. |
description | string | — |
Parameters from the server's own tool schema.
Why createPlanPhase is rated Medium
This tool creates new plan phases within a project management/company knowledge system. It modifies data (adds a new phase) but does not delete, execute arbitrary code, or cause financial transactions. The auto-computed position and WBS code suggest standard hierarchical planning operations.
From the tool's definition Tool name 'createPlanPhase' and description states it 'Create[s] a phase in a plan', which is a reversible creation of structured data within a planning system.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs createPlanPhase 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 createPlanPhase, this is the rule to start with:
createPlanPhase 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 createPlanPhase call is checked against it from then on.
Questions about createPlanPhase
Create a phase in a plan. Position and wbs_code are auto-computed. 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.
createPlanPhase accepts 10 parameters: name, color, planId, status, end_date, position, priority, wbs_code, start_date, description. Required: name, 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 createPlanPhase: 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.
createPlanPhase 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 createPlanPhase 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 createPlanPhase. 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.
createPlanPhase 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