deleteImprovementComment
Delete a comment from an improvement. Only its author, or an admin of the improvement's project, workspace or organisation, can delete it.
This record as markdown: /tools/io-stablebaseline-sb/deleteimprovementcomment.md
What deleteImprovementComment does on Stable Baseline
AI agents call deleteImprovementComment to permanently remove resources in Stable Baseline, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
activityId | string | Yes | Activity ID from getImprovement activity array. |
Parameters from the server's own tool schema.
Why deleteImprovementComment is rated Critical
An AI agent that decides to call deleteImprovementComment doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Stable Baseline is gone. There is no undo for destructive operations.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs deleteImprovementComment 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 deleteImprovementComment, this is the rule to start with:
deleteImprovementComment is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every deleteImprovementComment call is checked against it from then on.
Questions about deleteImprovementComment
Delete a comment from an improvement. Only its author, or an admin of the improvement's project, workspace or organisation, can delete it. It is categorised as a Destructive tool in the Stable Baseline MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteImprovementComment accepts 1 parameter: activityId. Required: activityId. 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 deleteImprovementComment: 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.
deleteImprovementComment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteImprovementComment 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 deleteImprovementComment. 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.
deleteImprovementComment 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.
Across the catalogue