search_docs

Search for Google Docs by name using Drive API

SERVERVaultAssist SOURCE3xcaffeine/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/3xcaffeine-mcp-server/search-docs.md

WHAT IT DOES

What search_docs does on VaultAssist

AI agents call search_docs to retrieve information from VaultAssist without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why search_docs is rated Low

This tool performs a search operation to retrieve documents by name. It is a non-destructive, side-effect-free query operation that only retrieves data from Google Drive, making it a Read category tool. The severity is low because unauthorized access to document metadata poses limited risk compared to data modification or deletion.

From the tool's definition Tool name 'search_docs' and description 'Search for Google Docs by name using Drive API' indicate a read-only query operation that retrieves documents without modifying, deleting, or executing any operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_docs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and VaultAssist, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_docs, this is the rule to start with:

search_docs Allowed

search_docs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_docs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultAssist, apply this rule, and every search_docs call is checked against it from then on.

FAQ

Questions about search_docs

What does the search_docs tool do? +

Search for Google Docs by name using Drive API. It is categorised as a Read tool in the VaultAssist MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_docs? +

Register the VaultAssist MCP server in PolicyLayer and add a rule for search_docs: 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.

What risk level is search_docs? +

search_docs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_docs? +

Yes. Add a rate_limit block to the search_docs 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.

How do I block search_docs completely? +

Set action: deny in the PolicyLayer policy for search_docs. 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.

What MCP server provides search_docs? +

search_docs 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.

KEEP EXPLORING

More on VaultAssist, and thousands of servers like it.

This server

All 79 VaultAssist tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →