createPlan
Create a plan in a project. Requires projectId and title.
This record as markdown: /tools/io-stablebaseline-sb/createplan.md
What createPlan does on Stable Baseline
AI agents use createPlan 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 |
|---|---|---|---|
icon | string | — | Lucide icon name. |
color | string | — | Color code. |
title | string | Yes | |
status | string | — | Status. Default: draft. |
end_date | string | — | YYYY-MM-DD. |
priority | string | — | Priority. Default: medium. |
projectId | string | Yes | |
start_date | string | — | YYYY-MM-DD. |
description | string | — | |
linked_documents | array | — | Array of {id, title}. |
linked_document_ids | array | — | Document IDs to link. |
Parameters from the server's own tool schema.
Why createPlan is rated Medium
The tool creates new data (a plan) within a project context, which is reversible (plans can be updated or deleted later). This is a Write operation. Severity is medium because creating plans in a company knowledge management system could affect project tracking and team workflows, but the impact is bounded to organizational planning artifacts rather than financial transactions, code execution, or irreversible…
From the tool's definition Tool name 'createPlan' and description 'Create a plan in a project' indicate a creation operation that modifies project data by adding a new plan artifact.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs createPlan 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 createPlan, this is the rule to start with:
createPlan 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 createPlan call is checked against it from then on.
Questions about createPlan
Create a plan in a project. Requires projectId and title. 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.
createPlan accepts 11 parameters: icon, color, title, status, end_date, priority, projectId, start_date, description, linked_documents, linked_document_ids. Required: title, projectId. 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 createPlan: 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.
createPlan 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 createPlan 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 createPlan. 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.
createPlan 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