This record as markdown: /tools/com-local-mcp-local-mcp/onedrive-write-file.md
What onedrive_write_file does on Local
AI agents use onedrive_write_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 |
|---|---|---|---|
path | string | Yes | Absolute path to the file in OneDrive |
confirm | boolean | — | Must be true to write |
content | string | Yes | Text content to write |
Parameters from the server's own tool schema.
Why onedrive_write_file is rated Medium
This tool creates or modifies files in OneDrive, which is a reversible write operation. While high severity due to potential for overwriting important documents or injecting malicious content into cloud storage accessible across devices/users, it does not irreversibly delete data (not Destructive), does not involve financial transactions (not Financial), and does not execute arbitrary code (not Execute).
From the tool's definition Tool name 'onedrive_write_file' and description 'Writes text content to a file in OneDrive' explicitly indicate data creation/modification to cloud storage.
Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs onedrive_write_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_write_file, this is the rule to start with:
onedrive_write_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_write_file call is checked against it from then on.
Questions about onedrive_write_file
Writes text content to a file in 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_write_file accepts 3 parameters: path, confirm, content. Required: path, content. 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_write_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_write_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_write_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_write_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_write_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