delete_onedrive_file
Delete a OneDrive item — it moves to the OneDrive recycle bin (recoverable there). Pass fileId (from list_onedrive_files) + confirm:true. Confirm the exact file with the user first.
This record as markdown: /tools/hermoso/delete-onedrive-file.md
What delete_onedrive_file does on Hermoso
AI agents call delete_onedrive_file to permanently remove resources in Hermoso, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_onedrive_file is rated Critical
This tool irreversibly removes files from a user's active OneDrive storage, even though OneDrive's recycle bin provides potential recovery within a retention window. The destructive category applies because the action cannot be undone by normal operations and requires explicit confirmation.
From the tool's definition delete_onedrive_file performs deletion via 'Delete a OneDrive item' — moving files to recycle bin. Although the tool documentation states files are 'recoverable there', the primary action is irreversible file deletion from active storage.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_onedrive_file, this is the rule to start with:
delete_onedrive_file is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hermoso, apply this rule, and every delete_onedrive_file call is checked against it from then on.
Questions about delete_onedrive_file
Delete a OneDrive item — it moves to the OneDrive recycle bin (recoverable there). Pass fileId (from list_onedrive_files) + confirm:true. Confirm the exact file with the user first. It is categorised as a Destructive tool in the Hermoso MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hermoso MCP server in PolicyLayer and add a rule for delete_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.
delete_onedrive_file is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue