deleteImprovement
Delete an improvement and all associated evidence and activity.
This record as markdown: /tools/io-stablebaseline-sb/deleteimprovement.md
What deleteImprovement does on Stable Baseline
AI agents call deleteImprovement 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 |
|---|---|---|---|
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 |
improvementId | string | Yes |
Parameters from the server's own tool schema.
Why deleteImprovement is rated Critical
This tool permanently removes data (improvements, evidence, and activity records) with no stated undo mechanism. While the blast radius is somewhat contained to improvement records within a knowledge/planning system rather than financial data or infrastructure, the irreversible nature and potential loss of organizational knowledge (evidence, activity trails) justifies the Destructive category and high severity.
From the tool's definition The tool description explicitly states it will 'Delete an improvement and all associated evidence and activity.' The verb 'delete' combined with the scope of deletion ('and all associated evidence and activity') indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs deleteImprovement 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 deleteImprovement, this is the rule to start with:
deleteImprovement 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 deleteImprovement call is checked against it from then on.
Questions about deleteImprovement
Delete an improvement and all associated evidence and activity. 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.
deleteImprovement accepts 2 parameters: projectId, improvementId. Required: improvementId. 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 deleteImprovement: 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.
deleteImprovement 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 deleteImprovement 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 deleteImprovement. 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.
deleteImprovement 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