addImprovementActivity
Add a comment or activity entry to an improvement.
This record as markdown: /tools/io-stablebaseline-sb/addimprovementactivity.md
What addImprovementActivity does on Stable Baseline
AI agents use addImprovementActivity 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 |
|---|---|---|---|
comment | string | — | Comment text. |
metadata | object | — | Additional context. |
newValue | string | — | For field_change: new value. |
oldValue | string | — | For field_change: previous value. |
fieldName | string | — | For field_change: field name. |
activityType | string | — | Type: comment, agent_update, field_change. Default: comment. |
improvementId | string | Yes |
Parameters from the server's own tool schema.
Why addImprovementActivity is rated Medium
This tool creates or modifies data in a reversible manner—adding comments or activity entries to improvements is a write operation. The blast radius is medium because malicious additions could clutter records, mislead teams about improvement status, or create false activity trails, but the operation is fully reversible (entries can be deleted or corrected).
From the tool's definition Tool name 'addImprovementActivity' and description 'Add a comment or activity entry to an improvement' indicate creation of new data entries (comments/activities) in a structured system.
Attacks that exploit this kind of access
The rule that runs addImprovementActivity 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 addImprovementActivity, this is the rule to start with:
addImprovementActivity 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 addImprovementActivity call is checked against it from then on.
Questions about addImprovementActivity
Add a comment or activity entry to an 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.
addImprovementActivity accepts 7 parameters: comment, metadata, newValue, oldValue, fieldName, activityType, improvementId. Required: improvementId. 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 addImprovementActivity: 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.
addImprovementActivity 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 addImprovementActivity 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 addImprovementActivity. 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.
addImprovementActivity 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