reorderDocuments

MOVE documents and boards between folders, or into another project of the organisation, and reorder them: the batch filing tool. Pass items [{documentId, folderId?, position?}, ...]. Inside a project give at least one of folderId or position per item: folderId MOVES that document into the given folder (null for the project's top level; omit it to leave the document where it is); position sets its place among its siblings (omit it to put the document at the end of wherever it lands, which is usually what you want when filing). To move documents or boards into ANOTHER project, in any workspace of the same organisation, also give projectId, the project they move to: each item's folderId then names a folder of that project (null or omitted for its top level) and each lands at the end of it (a position is not used there). Their pictures, diagrams, attachments, versions and links keep working, and their DOC and WBD numbers stay. Moving an item out of its project needs the right to delete it there or to be the one who made it, and the right to add where it goes; at most 500 items in one move. Give dryRun: true to see what would move and anything that would refuse, with nothing changed. The whole batch is applied in ONE atomic write, so it all lands or none of it does; a bad folderId or an unreachable documentId fails the call with nothing changed. Filing is metadata only: it does NOT create a new version. The response says where each document landed. For one document inside its project you can also use editDocument({documentId, folderId, position}); to move a whole folder with everything in it, use updateFolder({folderId, projectId}). 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.

reorderDocuments accepts 3 parameters: items, dryRun, projectId. Required: items. 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 reorderDocuments: 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.

reorderDocuments 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 reorderDocuments 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 reorderDocuments. 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.

reorderDocuments 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.