dropbox_search
Search Dropbox for files and folders by name.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/dropbox-search.md
What dropbox_search does on UnClick
AI agents call dropbox_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 | — | Results to return (max 1000, default 25) |
query | string | Yes | File or folder name to search for |
access_token | string | — | Dropbox access token |
Parameters from the server's own tool schema.
Why dropbox_search is rated Low
This tool retrieves information about files and folders in Dropbox based on search criteria. It performs a read-only query operation that has no side effects—it does not create, modify, delete, or execute anything. The search operation is a standard information retrieval action with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'dropbox_search' and description 'Search Dropbox for files and folders by name' indicate a query operation with no modification capability.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs dropbox_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 dropbox_search, this is the rule to start with:
dropbox_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 dropbox_search call is checked against it from then on.
Questions about dropbox_search
Search Dropbox for 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.
dropbox_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 dropbox_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.
dropbox_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 dropbox_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 dropbox_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.
dropbox_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