listDocumentVersions

SERVERStable Baseline SOURCEhttps://api.stablebaseline.io/functions/v1/cloud-serve/mcp

Low RISK CLASS

Category Read

Parameters 121 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-stablebaseline-sb/listdocumentversions.md

WHAT IT DOES

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).
`compare`	boolean	—	Also return the difference: the lines added and removed, each with the heading it sits under.
`fromDate`	string	—	ISO 8601 date filter (from).
`timeZone`	string	—	The IANA time zone the window and its times are in, such as Australia/Sydney. Default: the person's own (the zone their browser last saved), else UTC.
`projectId`	string	—	Optional. Narrows a friendly-id lookup to one project. Only needed when a friendly id is ambiguous — TAS-/IMP-/PLN- ids are numbered per PROJECT, so the same id
`documentId`	string	Yes	Accepts either the UUID or the friendly id (e.g. DOC-815); friendly ids are resolved within your organisation.
`changedSince`	string	—	What changed: only what was added or edited from this point, newest change first, each with who changed it and when. A period: today, yesterday, this_week, last
`changedBefore`	string	—	With changedSince given as a date: only what changed before this date (YYYY-MM-DD) or date and time.
`sortAscending`	boolean	—	Sort oldest first. Default: false.

Parameters from the server's own tool schema.

RISK

Why listDocumentVersions is rated Low

Even though listDocumentVersions only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHigh parameter count (13 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

listDocumentVersions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "listDocumentVersions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about listDocumentVersions

What does the listDocumentVersions tool do? +

List version history for a document. Returns timestamps, creator, change summary, and content. HOW IT CHANGED: give changedSince (a period such as this_week, or a date) for the versions saved in that time, each with who saved it by name and when in words; add compare:true for the difference, worked out from the text: the lines added and removed between the document as it stood before that time and now, each with the heading it sits under. compare:true without changedSince sets a version (versionNumber, else the newest) against the one before it. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.

What parameters does listDocumentVersions accept? +

listDocumentVersions accepts 12 parameters: limit, fields, offset, toDate, compare, fromDate, timeZone, projectId, documentId, changedSince, changedBefore, sortAscending. Required: documentId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on listDocumentVersions? +

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.

What risk level is listDocumentVersions? +

listDocumentVersions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit listDocumentVersions? +

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.

How do I block listDocumentVersions completely? +

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.

What MCP server provides listDocumentVersions? +

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.

KEEP EXPLORING

More on Stable Baseline, and thousands of servers like it.

This server

All 222 Stable Baseline tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →