This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/onedrive-search.md
What onedrive_search does on UnClick
AI agents call onedrive_search to retrieve information from UnClick 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 |
|---|---|---|---|
limit | number | — | Items to return (max 100, default 25) |
query | string | Yes | File or folder name to search for |
access_token | string | — | OneDrive access token |
Parameters from the server's own tool schema.
Why onedrive_search is rated Low
The tool retrieves and queries file/folder information from OneDrive without side effects. It performs a search operation, which is a non-destructive data retrieval action. No data is created, modified, deleted, or executed. The severity is low because search results themselves pose minimal risk when accessed by an AI agent, though the agent could theoretically identify sensitive files to target with other tools.
From the tool's definition Tool description states 'Search OneDrive files and folders by name' — a read-only query operation with no modification, deletion, or execution capability.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs onedrive_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For onedrive_search, this is the rule to start with:
onedrive_search 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 UnClick, apply this rule, and every onedrive_search call is checked against it from then on.
Questions about onedrive_search
Search OneDrive files and folders by name. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
onedrive_search accepts 3 parameters: limit, query, access_token. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for onedrive_search: 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 UnClick. Nothing to install.
onedrive_search 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_search 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_search. 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_search is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue