addImprovementEvidence
Add evidence to an improvement. Types: document_section, diagram_node, incident_note, feedback, free_text.
This record as markdown: /tools/io-stablebaseline-sb/addimprovementevidence.md
What addImprovementEvidence does on Stable Baseline
AI agents use addImprovementEvidence 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 |
|---|---|---|---|
refId | string | — | Reference ID (document, diagram, etc.). |
refUrl | string | — | Reference URL. |
summary | string | Yes | Summary of the evidence. |
position | number | — | Order in evidence list. |
rawContent | string | — | Full original text. |
evidenceType | string | — | Evidence type. Default: free_text. |
improvementId | string | Yes |
Parameters from the server's own tool schema.
Why addImprovementEvidence is rated Medium
This tool creates or appends new evidence records to an existing improvement, which is a reversible write operation. It does not delete, execute code, move money, or trigger external operations.
From the tool's definition Tool name 'addImprovementEvidence' and description 'Add evidence to an improvement' indicates creation/modification of data.
Attacks that exploit this kind of access
The rule that runs addImprovementEvidence 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 addImprovementEvidence, this is the rule to start with:
addImprovementEvidence 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 addImprovementEvidence call is checked against it from then on.
Questions about addImprovementEvidence
Add evidence to an improvement. Types: document_section, diagram_node, incident_note, feedback, free_text. 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.
addImprovementEvidence accepts 7 parameters: refId, refUrl, summary, position, rawContent, evidenceType, improvementId. Required: summary, 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 addImprovementEvidence: 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.
addImprovementEvidence 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 addImprovementEvidence 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 addImprovementEvidence. 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.
addImprovementEvidence 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