rename_drive_item
Rename a Drive item, meaning a file or folder, in its current folder. Idempotent when the title is unchanged. Rejects sibling title collisions; use move_drive_item to change folders.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/rename-drive-item.md
What rename_drive_item does on Huly
AI agents use rename_drive_item to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.
Why rename_drive_item is rated Medium
This tool modifies file/folder names reversibly. It is Write category because renaming is a metadata modification that can be undone (file can be renamed back). Severity is medium because an AI agent could rename critical files to confusing names or cause workflow disruption, but the operation is reversible and limited to the current folder.
From the tool's definition Tool renames files or folders in their current location. Description states "Rename a Drive item, meaning a file or folder" and notes it "Rejects sibling title collisions", confirming it modifies metadata of existing items rather than creating new ones or…
Attacks that exploit this kind of access
The rule that runs rename_drive_item safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rename_drive_item, this is the rule to start with:
rename_drive_item 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 Huly, apply this rule, and every rename_drive_item call is checked against it from then on.
Questions about rename_drive_item
Rename a Drive item, meaning a file or folder, in its current folder. Idempotent when the title is unchanged. Rejects sibling title collisions; use move_drive_item to change folders. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huly MCP server in PolicyLayer and add a rule for rename_drive_item: 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 Huly. Nothing to install.
rename_drive_item 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 rename_drive_item 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 rename_drive_item. 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.
rename_drive_item is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue