listDocumentVersions
List version history for a document. Returns timestamps, creator, change summary, and content.
This record as markdown: /tools/io-stablebaseline-sb/listdocumentversions.md
What listDocumentVersions does on Stable Baseline
AI agents call listDocumentVersions to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max versions. Default: 50, max: 200. |
fields | array | — | Field projection. Valid fields: id, documentId, versionNumber, title, contentMarkdown, changeSummary, createdBy, createdAt. |
offset | number | — | Pagination offset. |
toDate | string | — | ISO 8601 date filter (to). |
fromDate | string | — | ISO 8601 date filter (from). |
documentId | string | Yes | |
sortAscending | boolean | — | Sort oldest first. Default: false. |
versionNumber | number | — | Filter to a specific version. |
Parameters from the server's own tool schema.
Why listDocumentVersions is rated Low
This is a Read operation that queries document version metadata and historical content. The 'medium' severity reflects that version history may contain sensitive business information (plans, strategies, past decisions) that could be valuable to an attacker or misused AI agent, but the tool itself is read-only with no side effects or data modification capability.
From the tool's definition Tool 'listDocumentVersions' retrieves and returns version history data including 'timestamps, creator, change summary, and content' with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs listDocumentVersions 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 listDocumentVersions, this is the rule to start with:
listDocumentVersions is read-only, so it stays allowed. 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 listDocumentVersions call is checked against it from then on.
Questions about listDocumentVersions
List version history for a document. Returns timestamps, creator, change summary, and content. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listDocumentVersions accepts 8 parameters: limit, fields, offset, toDate, fromDate, documentId, sortAscending, versionNumber. Required: documentId. 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 listDocumentVersions: 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.
listDocumentVersions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listDocumentVersions 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 listDocumentVersions. 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.
listDocumentVersions 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