AI agents call list_docs_in_folder 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 performs a read-only operation that retrieves and displays information about documents in a Drive folder. It has no side effects, does not modify or delete data, and does not execute code or move money. The blast radius of misuse is minimal—an agent could view documents it shouldn't access, but cannot alter or destroy them. This is a classic Read category tool.
From the tool's definition Tool name is 'list_docs_in_folder' and description states 'List Google Docs within a specific Drive folder' — listing/querying operations with no modification or deletion capability.
Documented attack patterns abuse exactly the kind of access list_docs_in_folder 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_docs_in_folder:
{
"version": "1",
"default": "deny",
"tools": {
"list_docs_in_folder": {}
}
}list_docs_in_folder 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 Google Docs within a specific 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_docs_in_folder: 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_docs_in_folder 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_docs_in_folder 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_docs_in_folder. 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_docs_in_folder 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.