This record as markdown: /tools/com-local-mcp-local-mcp/onedrive-root.md
What onedrive_root does on Local
AI agents call onedrive_root 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.
Why onedrive_root is rated Low
This tool performs a simple enumeration of existing OneDrive mount points on the system. It has no side effects, does not modify data, and does not execute code or commands. The blast radius of misuse is minimal; an attacker could learn what OneDrive directories are accessible but cannot directly access their contents, modify data, or cause damage through this tool alone. It is a straightforward Read operation.
From the tool's definition Tool description states 'Lists all mounted OneDrive directories' — a read-only operation that retrieves information about mounted directories without modification.
Attacks that exploit this kind of access
The rule that runs onedrive_root 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_root, this is the rule to start with:
onedrive_root 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_root call is checked against it from then on.
Questions about onedrive_root
Lists all mounted OneDrive directories on this Mac. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
Register the Local MCP server in PolicyLayer and add a rule for onedrive_root: 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_root 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_root 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_root. 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_root 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