deleteImprovementCategory
Delete an improvement category. Cannot delete system categories.
This record as markdown: /tools/io-stablebaseline-sb/deleteimprovementcategory.md
What deleteImprovementCategory does on Stable Baseline
AI agents call deleteImprovementCategory 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 |
|---|---|---|---|
categoryId | string | Yes |
Parameters from the server's own tool schema.
Why deleteImprovementCategory is rated Critical
This tool permanently removes an improvement category from the system, which cannot be undone. While the tool has a safeguard preventing deletion of system categories, it still allows deletion of user-created categories, resulting in irreversible data loss. This qualifies as Destructive rather than Write (which are reversible operations).
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete an improvement category.' The verb 'delete' combined with the action of removing a category from the system indicates irreversible data removal.
Attacks that exploit this kind of access
The rule that runs deleteImprovementCategory 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 deleteImprovementCategory, this is the rule to start with:
deleteImprovementCategory 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 deleteImprovementCategory call is checked against it from then on.
Questions about deleteImprovementCategory
Delete an improvement category. Cannot delete system categories. 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.
deleteImprovementCategory accepts 1 parameter: categoryId. Required: categoryId. 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 deleteImprovementCategory: 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.
deleteImprovementCategory 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 deleteImprovementCategory 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 deleteImprovementCategory. 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.
deleteImprovementCategory 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