List files and folders in a specific Google Drive folder
AI agents call list_drive_items to retrieve information from VaultAssist without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves directory contents from Google Drive without creating, modifying, deleting, or executing anything. While it operates on user data within a multi-user system, the information exposure is limited to the authenticated user's own Drive contents or shared folders they have read access to.
From the tool's definition Tool description explicitly states 'List files and folders' which is a retrieval operation with no data modification. The verb 'list' is a canonical Read operation.
Documented attack patterns abuse exactly the kind of access list_drive_items gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VaultAssist, and nothing reaches the server without passing your rules. This is the rule we recommend for list_drive_items:
{
"version": "1",
"default": "deny",
"tools": {
"list_drive_items": {}
}
}list_drive_items is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List files and folders in a specific Google Drive folder. It is categorised as a Read tool in the VaultAssist MCP Server, which means it retrieves data without modifying state.
Register the VaultAssist MCP server in PolicyLayer and add a rule for list_drive_items: 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 VaultAssist. Nothing to install.
list_drive_items 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 list_drive_items 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 list_drive_items. 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.
list_drive_items is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VaultAssist, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
79 VaultAssist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.