listImprovementCategories
List improvement categories for a project. Returns tree and flat list.
This record as markdown: /tools/io-stablebaseline-sb/listimprovementcategories.md
What listImprovementCategories does on Stable Baseline
AI agents call listImprovementCategories to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectId | string | Yes |
Parameters from the server's own tool schema.
Why listImprovementCategories is rated Low
This tool retrieves and lists existing improvement categories, presenting them in multiple formats (tree and flat list). It performs no modifications, deletions, or external operations. The action is read-only with no data mutation or destructive potential. Low severity reflects minimal blast radius even if invoked inappropriately by an agent.
From the tool's definition Tool name 'listImprovementCategories' and description 'List improvement categories for a project. Returns tree and flat list.' indicate a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs listImprovementCategories 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 listImprovementCategories, this is the rule to start with:
listImprovementCategories is read-only, so it stays allowed. 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 listImprovementCategories call is checked against it from then on.
Questions about listImprovementCategories
List improvement categories for a project. Returns tree and flat list. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listImprovementCategories accepts 1 parameter: projectId. Required: 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 listImprovementCategories: 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.
listImprovementCategories is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listImprovementCategories 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 listImprovementCategories. 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.
listImprovementCategories 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