update_onedrive_file
Update a OneDrive item: rename (name) and/or move it into a folder (moveToFolderId). Pass fileId (from list_onedrive_files). To remove an item, use delete_onedrive_file.
This record as markdown: /tools/hermoso/update-onedrive-file.md
What update_onedrive_file does on Hermoso
AI agents use update_onedrive_file to create or update resources in Hermoso, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hermoso environment.
Why update_onedrive_file is rated Medium
This tool modifies file properties (name and folder location) in OneDrive but does not create new content, execute code, delete data, or handle financial transactions. These are reversible Write operations with moderate blast radius if misused by an agent (could rename/relocate files belonging to the user or their organization, causing confusion or disruption, but changes are undoable).
From the tool's definition Tool description states it can 'rename' and 'move' OneDrive items, which are reversible modifications to file metadata and location.
Attacks that exploit this kind of access
The rule that runs update_onedrive_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hermoso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_onedrive_file, this is the rule to start with:
update_onedrive_file 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 Hermoso, apply this rule, and every update_onedrive_file call is checked against it from then on.
Questions about update_onedrive_file
Update a OneDrive item: rename (name) and/or move it into a folder (moveToFolderId). Pass fileId (from list_onedrive_files). To remove an item, use delete_onedrive_file. It is categorised as a Write tool in the Hermoso MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hermoso MCP server in PolicyLayer and add a rule for update_onedrive_file: 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 Hermoso. Nothing to install.
update_onedrive_file 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_onedrive_file 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_onedrive_file. 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_onedrive_file is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hermoso, and thousands of servers like it.
This server
Across the catalogue