update_folder
Use this when the user wants to rename, re-describe, or move (reparent) an existing Cloud Analytics folder. Changes apply immediately. Auto-renaming on collision applies only when moving to another parent; a rename that collides with a sibling is rejected. Invalid parents and moves into self or a...
This record as markdown: /tools/doit/update-folder.md
What update_folder does on Doit
AI agents use update_folder to create or update resources in Doit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doit environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | The ID of the folder to update (required). |
name | string | — | New name for the folder. |
description | string | null | — | New description for the folder. Empty string clears; omission or null leaves unchanged. |
parentFolderId | string | — | The ID of the new parent folder, or "root" to move to the top level. |
Parameters from the server's own tool schema.
Why update_folder is rated Medium
An AI agent can call update_folder faster than any human can review: one bad instruction and it creates or modifies resources in Doit by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs update_folder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_folder, this is the rule to start with:
update_folder 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 Doit, apply this rule, and every update_folder call is checked against it from then on.
Questions about update_folder
Use this when the user wants to rename, re-describe, or move (reparent) an existing Cloud Analytics folder. Changes apply immediately. Auto-renaming on collision applies only when moving to another parent; a rename that collides with a sibling is rejected. Invalid parents and moves into self or a descendant are rejected. Do NOT use this for creating new folders (use create_folder) or updating reports (use update_report). It is categorised as a Write tool in the Doit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_folder accepts 4 parameters: id, name, description, parentFolderId. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Doit MCP server in PolicyLayer and add a rule for update_folder: 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 Doit. Nothing to install.
update_folder 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 update_folder 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 update_folder. 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.
update_folder is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Doit, and thousands of servers like it.
This server
Across the catalogue