reorderFolders
Batch-reorder folders within a parent (or project root) by setting sibling positions. Pass [{folderId, position}, ...] where position is a non-negative integer; usually you renumber siblings sequentially as 0, 1, 2…. To MOVE a folder to a different parent and set its position there, use updateFol...
This record as markdown: /tools/io-stablebaseline-sb/reorderfolders.md
What reorderFolders does on Stable Baseline
AI agents use reorderFolders 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 |
|---|---|---|---|
items | array | Yes | List of folder position updates. All folders must belong to the same project. |
Parameters from the server's own tool schema.
Why reorderFolders is rated Medium
The tool creates or modifies data (folder positions) reversibly. It does not delete, execute code, move money, or trigger irreversible operations. Reordering is a Write operation. Severity is medium because misuse could disorganize project structure and impede workflow, but changes are fully reversible.
From the tool's definition Tool description states 'Batch-reorder folders within a parent' and 'renumber siblings sequentially'. The operation modifies folder positions/metadata, which is reversible via re-reordering.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs reorderFolders 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 reorderFolders, this is the rule to start with:
reorderFolders 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 reorderFolders call is checked against it from then on.
Questions about reorderFolders
Batch-reorder folders within a parent (or project root) by setting sibling positions. Pass [{folderId, position}, ...] where position is a non-negative integer; usually you renumber siblings sequentially as 0, 1, 2…. To MOVE a folder to a different parent and set its position there, use updateFolder({parentId, position}) instead. 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.
reorderFolders accepts 1 parameter: items. 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 reorderFolders: 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.
reorderFolders 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 reorderFolders 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 reorderFolders. 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.
reorderFolders 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