deletePlan
Delete a plan, all its phases, and all tasks/improvements within it. This is a destructive operation that cannot be undone.
This record as markdown: /tools/io-stablebaseline-sb/deleteplan.md
What deletePlan does on Stable Baseline
AI agents call deletePlan to permanently remove resources in Stable Baseline, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
planId | string | Yes | |
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 deletePlan is rated Critical
This tool permanently removes entire plans and their associated data structures (phases, tasks, improvements) with no recovery mechanism. It matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' Severity is high because the blast radius affects multiple interconnected data objects and work items, but not critical since it's scoped to a single plan…
From the tool's definition Tool description explicitly states: 'Delete a plan, all its phases, and all tasks/improvements within it. This is a destructive operation that cannot be undone.' The use of 'Delete' and 'cannot be undone' directly indicates irreversible data destruction.
Attacks that exploit this kind of access
The rule that runs deletePlan 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 deletePlan, this is the rule to start with:
deletePlan is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every deletePlan call is checked against it from then on.
Questions about deletePlan
Delete a plan, all its phases, and all tasks/improvements within it. This is a destructive operation that cannot be undone. It is categorised as a Destructive tool in the Stable Baseline MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deletePlan 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 deletePlan: 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.
deletePlan is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deletePlan 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 deletePlan. 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.
deletePlan 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.
Across the catalogue