This record as markdown: /tools/com-local-mcp-local-mcp/onedrive-move-file.md
What onedrive_move_file does on Local
AI agents use onedrive_move_file to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
source | string | Yes | Source path |
confirm | boolean | — | Must be true to move |
destination | string | Yes | Destination path |
Parameters from the server's own tool schema.
Why onedrive_move_file is rated Medium
Moving and renaming files are write operations that modify data structure and organization but remain fully reversible. The user can move files back to original locations or restore previous names. This is less severe than destructive actions (deletion/purge) but impacts data organization.
From the tool's definition Tool performs 'Moves or renames a file/folder within OneDrive' — these are reversible modifications to file metadata and location within a cloud storage system.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs onedrive_move_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_move_file, this is the rule to start with:
onedrive_move_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 Local, apply this rule, and every onedrive_move_file call is checked against it from then on.
Questions about onedrive_move_file
Moves or renames a file/folder within OneDrive. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
onedrive_move_file accepts 3 parameters: source, confirm, destination. Required: source, destination. 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_move_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_move_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 onedrive_move_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_move_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_move_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.
This server
Across the catalogue