updateFolder
Update a folder (rename/move/reorder). Supports nesting changes via parentId.
This record as markdown: /tools/io-stablebaseline-sb/updatefolder.md
What updateFolder does on Stable Baseline
AI agents use updateFolder 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 |
|---|---|---|---|
name | string | — | |
folderId | string | Yes | |
parentId | string | — | |
position | number | — |
Parameters from the server's own tool schema.
Why updateFolder is rated Medium
The tool modifies folder properties (name, location, hierarchy) but does not delete data or trigger external operations. Changes are reversible—folders can be renamed back, moved to original locations, or reordered again. This fits the Write category (creates or modifies data reversibly).
From the tool's definition Tool description states 'Update a folder (rename/move/reorder)' and supports 'nesting changes via parentId'. These are reversible modifications to folder metadata and structure within a document/knowledge management system.
Attacks that exploit this kind of access
The rule that runs updateFolder 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 updateFolder, this is the rule to start with:
updateFolder 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 updateFolder call is checked against it from then on.
Questions about updateFolder
Update a folder (rename/move/reorder). Supports nesting changes via parentId. 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.
updateFolder accepts 4 parameters: name, folderId, parentId, position. Required: folderId. 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 updateFolder: 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.
updateFolder 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 updateFolder 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 updateFolder. 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.
updateFolder 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