listImprovements
List AND grep improvements in a project. query searches the title, friendlyId and problem statement, not just the title (substring by default; set isRegex:true for a regular expression, caseSensitive:true for exact case). Supports filtering by status, type, priority. For ranked semantic + text se...
This record as markdown: /tools/io-stablebaseline-sb/listimprovements.md
What listImprovements does on Stable Baseline
AI agents call listImprovements 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 |
|---|---|---|---|
type | string | — | Filter: feature, bug, tech_debt, architecture_gap, documentation_gap, risk, enhancement, task. Tasks (is_task=true) always have type='task'. |
limit | number | — | Max results (1-100, default 50). |
query | string | — | Grep across title, friendlyId and problem_statement. Substring by default; a regular expression when isRegex:true; case-insensitive unless caseSensitive:true. |
fields | array | — | Field projection. Valid fields: id, friendly_id, friendlyId, title, type, status, priority, source, category_id, categoryId, created_at, createdAt, updated_at, |
offset | number | — | Pagination offset. |
source | string | — | Filter: agent_review, human_manual, doc_comment, feedback, incident, etc. |
status | string | — | Filter: captured, triaging, shaped, approved, ready_for_agent, in_progress, ready_for_review, in_review, blocked, done, rejected, deferred. |
isRegex | boolean | — | Treat query as a regular expression (grep -E), e.g. "ACME-\d+". Default false (literal substring). |
priority | string | — | Filter: low, medium, high, critical. |
projectId | string | Yes | |
scanRunId | string | — | Filter by compliance scan run. |
sortField | string | — | Sort field. Default: position. |
Parameters from the server's own tool schema.
Why listImprovements is rated Low
This tool retrieves and filters existing improvement records. The grep/search, substring matching, regex support, and filtering operations are all read-only data retrieval with no side effects. No data is created, modified, deleted, or executed. Blast radius of misuse is limited to information disclosure.
From the tool's definition Tool name 'listImprovements' and description explicitly states 'List AND grep improvements' with query/search functionality. Operations described are: searching title, friendlyId, problem statement; filtering by status, type, priority.
Risk signalsHigh parameter count (18 properties)
Attacks that exploit this kind of access
The rule that runs listImprovements 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 listImprovements, this is the rule to start with:
listImprovements 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 listImprovements call is checked against it from then on.
Questions about listImprovements
List AND grep improvements in a project. query searches the title, friendlyId and problem statement, not just the title (substring by default; set isRegex:true for a regular expression, caseSensitive:true for exact case). Supports filtering by status, type, priority. For ranked semantic + text search use searchImprovements. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listImprovements accepts 12 parameters: type, limit, query, fields, offset, source, status, isRegex, priority, projectId, scanRunId, sortField. 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 listImprovements: 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.
listImprovements 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 listImprovements 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 listImprovements. 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.
listImprovements 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