This record as markdown: /tools/com-local-mcp-local-mcp/onedrive-delete-file.md
What onedrive_delete_file does on Local
AI agents call onedrive_delete_file to permanently remove resources in Local, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Absolute path to the file or folder |
confirm | boolean | — | Must be true to delete |
Parameters from the server's own tool schema.
Why onedrive_delete_file is rated Critical
The tool removes files from cloud storage without recovery options. Even though it only deletes empty folders, file deletion is irreversible and constitutes a destructive action. The high severity reflects the potential for permanent data loss if an AI agent misuses this capability without proper user intent verification. Destructive category takes precedence over Write since deletion cannot be undone.
From the tool's definition Tool name explicitly states 'delete_file' and description confirms 'Deletes a file or empty folder from OneDrive.' This is an irreversible data deletion operation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs onedrive_delete_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For onedrive_delete_file, this is the rule to start with:
onedrive_delete_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 Local, apply this rule, and every onedrive_delete_file call is checked against it from then on.
Questions about onedrive_delete_file
Deletes a file or empty folder from OneDrive. It is categorised as a Destructive tool in the Local MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
onedrive_delete_file accepts 2 parameters: path, confirm. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for onedrive_delete_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 Local. Nothing to install.
onedrive_delete_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 onedrive_delete_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 onedrive_delete_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.
onedrive_delete_file is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
Across the catalogue