createImprovement

SERVERStable Baseline SOURCEhttps://api.stablebaseline.io/functions/v1/cloud-serve/mcp

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-stablebaseline-sb/createimprovement.md

WHAT IT DOES

What createImprovement does on Stable Baseline

AI agents use createImprovement 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
`type`	string	—	Type. Default: enhancement. One of: feature (New capability for users); enhancement (An improvement to something that already exists); bug (Something that does
`title`	string	Yes
`fields`	array	—	Optional. Answer with only these fields instead of the whole improvement, for example ["id", "versionTimestamp"]. Any of the improvement's own fields (snake_cas
`source`	string	—	Where the work came from. Default: human_manual (shown as a general item), which is right for anything you raise yourself. Use feedback, incident, postmortem, c
`status`	string	—	Initial status. Default: captured.
`details`	object	—	The type's own fields. On update they MERGE key by key: keys you leave out are kept and null removes one. epic: success_measures. user_story: as_a, i_want, so_t
`is_task`	boolean	—	Mark as task. Default: false. Prefer setting type='task' instead: is_task follows the type automatically, and the friendly id's prefix follows the type too (see
`plan_id`	string	—	Link to a plan.
`urgency`	string	—	e.g. this_week, this_month, this_quarter.
`why_now`	string	—
`end_date`	string	—	YYYY-MM-DD.
`metadata`	object	—	Free-form JSON stored alongside the item. On updateImprovement this MERGES rather than replaces.

Parameters from the server's own tool schema.

RISK

Why createImprovement is rated Medium

An AI agent can call createImprovement faster than any human can review: one bad instruction and it creates or modifies resources in Stable Baseline by the hundred, each call as confident as the last.

Risk signalsAccepts freeform code/query input (details.statement) · High parameter count (83 properties) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs createImprovement 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 createImprovement, this is the rule to start with:

createImprovement Rate-limited

createImprovement 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "createImprovement": {
      "limits": [
        {
          "counter": "createimprovement_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every createImprovement call is checked against it from then on.

FAQ

Questions about createImprovement

What does the createImprovement tool do? +

Create an improvement item in a project. Requires projectId and title. Auto-assigns friendly ID. Accepts every field updateImprovement accepts, so an item can be created complete in one call rather than create-then-update. Pass parentItemId to create it under its epic or story in the work hierarchy, and linkedRecords to link database rows to it. Pass fields (for example ["id", "friendlyId", "versionTimestamp"]) for a short answer instead of the whole improvement. 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.

What parameters does createImprovement accept? +

createImprovement accepts 12 parameters: type, title, fields, source, status, details, is_task, plan_id, urgency, why_now, end_date, metadata. Required: title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on createImprovement? +

Register the Stable Baseline MCP server in PolicyLayer and add a rule for createImprovement: 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.

What risk level is createImprovement? +

createImprovement is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit createImprovement? +

Yes. Add a rate_limit block to the createImprovement 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.

How do I block createImprovement completely? +

Set action: deny in the PolicyLayer policy for createImprovement. 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.

What MCP server provides createImprovement? +

createImprovement 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.

KEEP EXPLORING

More on Stable Baseline, and thousands of servers like it.

This server

All 222 Stable Baseline tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →