createImprovementCategory
Create an improvement category or sub-category. Max two levels.
This record as markdown: /tools/io-stablebaseline-sb/createimprovementcategory.md
What createImprovementCategory does on Stable Baseline
AI agents use createImprovementCategory 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. |
name | string | Yes | |
slug | string | — | URL-friendly slug. Auto-generated if omitted. |
color | string | — | Color code. |
parentId | string | — | Parent category ID for sub-categories. |
projectId | string | Yes | |
sortOrder | number | — | Sort order. Default: 0. |
description | string | — |
Parameters from the server's own tool schema.
Why createImprovementCategory is rated Medium
This tool creates new organizational metadata (improvement categories) in the system. It is reversible (categories can be deleted or modified), affects no external systems, involves no financial transactions, does not execute arbitrary code, and does not destroy data. The blast radius of misuse is limited to potentially cluttering the category structure, which would be low-impact.
From the tool's definition Tool name and description indicate "Create an improvement category" which creates new data. The description specifies structural creation (category/sub-category) with defined constraints (max two levels), implying reversible data insertion into the knowledge…
Attacks that exploit this kind of access
The rule that runs createImprovementCategory 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 createImprovementCategory, this is the rule to start with:
createImprovementCategory 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 createImprovementCategory call is checked against it from then on.
Questions about createImprovementCategory
Create an improvement category or sub-category. Max two levels. 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.
createImprovementCategory accepts 8 parameters: icon, name, slug, color, parentId, projectId, sortOrder, description. Required: name, 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 createImprovementCategory: 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.
createImprovementCategory 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 createImprovementCategory 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 createImprovementCategory. 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.
createImprovementCategory 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