updateFolder

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

Medium RISK CLASS

Category Write

Parameters 61 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

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	—
`dryRun`	boolean	—	Optional. true answers what would move and anything that would refuse, and changes nothing.
`folderId`	string	Yes
`parentId`	string	—	The folder to move it under: in its own project, or with projectId in that project. Null for the top level.
`position`	number	—
`projectId`	string	—	Optional. The project to move the folder into, with everything in it: another project, in any workspace of the same organisation.

Parameters from the server's own tool schema.

RISK

Why updateFolder is rated Medium

An AI agent can call updateFolder faster than any human can review: one bad instruction and it creates or modifies resources in Stable Baseline by the hundred, each call as confident as the last.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "updateFolder": {
      "limits": [
        {
          "counter": "updatefolder_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about updateFolder

What does the updateFolder tool do? +

Update a folder: rename it, move it or reorder it. parentId moves it under another folder of its project. To move the folder WITH EVERYTHING IN IT into another project, in any workspace of the same organisation, give projectId (the project it moves to) and, if you like, parentId (a folder of that project; omit it for the project's top level). Its subfolders, documents and boards go with it, and their pictures, diagrams, attachments, versions and links keep working; their DOC and WBD numbers stay. Moving it out of its project needs, for the folder and everything in it, 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, all of it or none of it. Rename or reorder in a separate call. Give dryRun: true to see what would move and anything that would refuse, with nothing changed. 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.

What parameters does updateFolder accept? +

updateFolder accepts 6 parameters: name, dryRun, folderId, parentId, position, projectId. Required: folderId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on updateFolder? +

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.

What risk level is updateFolder? +

updateFolder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit updateFolder? +

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.

How do I block updateFolder completely? +

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.

What MCP server provides updateFolder? +

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.

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

Govern customer-ops agents →Argument validation →Scoped token →