onedrive_read_file
Reads a text file from OneDrive or the local filesystem. Supports .txt, .md, .csv, .json, .xml, .log and several code file types. Auto-detects UTF-8, falls back to Latin-1/Windows-1252 for legacy files (common in Latin American banking .TXT padrones).
This record as markdown: /tools/com-local-mcp-local-mcp/onedrive-read-file.md
What onedrive_read_file does on Local
AI agents call onedrive_read_file to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Absolute path to the file |
offset | integer | — | Start reading at byte offset (default 0) |
encoding | string | — | Force a specific encoding: 'auto' (default), 'utf8', 'latin1', 'cp1252', 'ascii', 'utf16' |
max_bytes | integer | — | Maximum bytes to read (default 1048576 = 1 MB, capped at 10485760 = 10 MB) |
Parameters from the server's own tool schema.
Why onedrive_read_file is rated Low
This is a Read operation—it retrieves file contents without side effects. Severity is medium rather than low because it accesses both OneDrive and local filesystem, which could expose sensitive data (email attachments, financial documents, credentials) if an AI agent is misled into reading unintended files. The mention of 'banking .TXT padrones' suggests access to potentially sensitive financial records.
From the tool's definition Tool name is 'onedrive_read_file' and description states it 'Reads a text file from OneDrive or the local filesystem' with no mention of modification, deletion, or execution. The action is retrieval only.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs onedrive_read_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_read_file, this is the rule to start with:
onedrive_read_file is read-only, so it stays allowed. 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_read_file call is checked against it from then on.
Questions about onedrive_read_file
Reads a text file from OneDrive or the local filesystem. Supports .txt, .md, .csv, .json, .xml, .log and several code file types. Auto-detects UTF-8, falls back to Latin-1/Windows-1252 for legacy files (common in Latin American banking .TXT padrones). It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
onedrive_read_file accepts 4 parameters: path, offset, encoding, max_bytes. 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_read_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_read_file is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the onedrive_read_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_read_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_read_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