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, and by parentItemId for an it...
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 by type: feature, enhancement, bug, tech_debt, architecture_gap, documentation_gap, risk, epic, user_story, requirement, test_case, spike, task. Tasks (i |
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, parent_item_id, parentItemId, paren |
offset | number | — | Pagination offset. |
source | string | — | Filter by source: human_manual, agent_review, doc_comment, feedback, incident, postmortem, code_review, imported. agent_review is the Compliance view; 'other' i |
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. |
timeZone | string | — | The IANA time zone the window and its times are in, such as Australia/Sydney. Default: the person's own (the zone their browser last saved), else UTC. |
projectId | string | — | |
scanRunId | string | — | Filter by compliance scan run. |
Parameters from the server's own tool schema.
Why listImprovements is rated Low
Even though listImprovements only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (26 properties) · Bulk/mass operation — affects multiple targets
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, and by parentItemId for an item's children in the work hierarchy (an epic's stories, say). For ranked semantic + text search use searchImprovements. Every item carries its versionTimestamp, ready for updateImprovement, so one call here supplies the tokens for a whole batch of updates (fields ["id", "friendlyId", "versionTimestamp"] returns just those), and its parentItem: the item it belongs to in the work hierarchy ({ id, friendlyId, title, type, status, isTask }, or null). Each item also carries linkedRecords, the database rows it links (as getImprovement describes them); filter by them with hasLinkedRecords, linkedRecordIds and linkedTableIds. projectId is required unless changedSince is given. WHAT CHANGED: give changedSince (a period such as this_week, or a date) to list only the improvements and tasks added or changed in that time, newest change first, each with change: what happened, when (in words, in the person's time zone), by whom (a person's name, and the agent's key when one did it), and what happened to each in that time in words (status and field changes, comments, evidence). With no project named it covers a workspace (workspaceId) or your whole organisation. Only what the caller may open is listed. With changedSince the filters are status, type, priority, source, categoryId and query. 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, timeZone, projectId, scanRunId. 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