drive_list_files
List files in a drive (by drive name or drv_… id), optionally under a path prefix.
This record as markdown: /tools/ai-dataecho-mcp/drive-list-files.md
What drive_list_files does on Mcp
AI agents call drive_list_files to retrieve information from Mcp 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 |
|---|---|---|---|
drive | string | Yes | Drive name or drv_… id |
prefix | string | — | Path prefix filter |
Parameters from the server's own tool schema.
Why drive_list_files is rated Low
This tool retrieves and lists file metadata from a drive storage system. It performs no write, delete, execute, or financial operations—only data retrieval. The blast radius of misuse is minimal (information disclosure limited to file names and structure visible within a drive the user already has access to).
From the tool's definition Tool name 'drive_list_files' and description 'List files in a drive' indicate retrieval of directory contents without modification. 'Optionally under a path prefix' confirms query-only semantics.
Attacks that exploit this kind of access
The rule that runs drive_list_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drive_list_files, this is the rule to start with:
drive_list_files 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 Mcp, apply this rule, and every drive_list_files call is checked against it from then on.
Questions about drive_list_files
List files in a drive (by drive name or drv_… id), optionally under a path prefix. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
drive_list_files accepts 2 parameters: drive, prefix. Required: drive. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for drive_list_files: 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 Mcp. Nothing to install.
drive_list_files 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 drive_list_files 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 drive_list_files. 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.
drive_list_files is provided by the MCP server (https://dataecho.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue