Low Risk

search_gdrive

Search for files in Google Drive

How to control search_gdrive ↓

What search_gdrive does on Google Toolbox

AI agents call search_gdrive to retrieve information from Google Toolbox without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_gdrive needs a policy

This tool performs a search operation on Google Drive, which is a read-only action that retrieves file metadata or listings. It has no side effects, does not execute code, does not modify or delete data, and poses minimal security risk. The blast radius of misuse is limited to potential disclosure of file names or metadata that an AI might already have access to.

From the tool's definition Tool name is 'search_gdrive' and description states 'Search for files in Google Drive'. The verb 'search' indicates a query operation that retrieves information without modifying or deleting data.

Documented attack patterns abuse exactly the kind of access search_gdrive gives an agent:

How to control search_gdrive

PolicyLayer is an MCP gateway — it sits between your AI agents and Google Toolbox, and nothing reaches the server without passing your rules. This is the rule we recommend for search_gdrive:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_gdrive": {}
  }
}

search_gdrive is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Google Toolbox — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_gdrive

What does the search_gdrive tool do? +

Search for files in Google Drive. It is categorised as a Read tool in the Google Toolbox MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_gdrive? +

Register the Google Toolbox MCP server in PolicyLayer and add a rule for search_gdrive: 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 Google Toolbox. Nothing to install.

What risk level is search_gdrive? +

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

Can I rate-limit search_gdrive? +

Yes. Add a rate_limit block to the search_gdrive 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_gdrive completely? +

Set action: deny in the PolicyLayer policy for search_gdrive. 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_gdrive? +

search_gdrive is provided by the Google Toolbox MCP server (jikime/py-mcp-google-toolbox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Toolbox tool call.

Start from Google Toolbox, 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.

11 Google Toolbox tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.