updateImprovementComment
Update a comment on an improvement. Requires the comment's updated_at as versionTimestamp.
This record as markdown: /tools/io-stablebaseline-sb/updateimprovementcomment.md
What updateImprovementComment does on Stable Baseline
AI agents use updateImprovementComment 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 | Yes | New comment text. |
activityId | string | Yes | Activity ID from getImprovement activity array. |
versionTimestamp | number | Yes | Comment's updated_at as Unix ms for optimistic locking. |
Parameters from the server's own tool schema.
Why updateImprovementComment is rated Medium
The tool creates or modifies data reversibly by updating an existing comment. It requires a version timestamp (updated_at) to perform the update, suggesting optimistic locking or version control to prevent conflicts. This is a classic Write operation.
From the tool's definition Tool name contains 'update' and description explicitly states 'Update a comment on an improvement.' This is a modification operation on existing data (a comment), not a retrieval or deletion.
Attacks that exploit this kind of access
The rule that runs updateImprovementComment 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 updateImprovementComment, this is the rule to start with:
updateImprovementComment 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 updateImprovementComment call is checked against it from then on.
Questions about updateImprovementComment
Update a comment on an improvement. Requires the comment's updated_at as versionTimestamp. 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.
updateImprovementComment accepts 3 parameters: comment, activityId, versionTimestamp. Required: comment, activityId, versionTimestamp. 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 updateImprovementComment: 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.
updateImprovementComment 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 updateImprovementComment 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 updateImprovementComment. 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.
updateImprovementComment 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