gdrive_root

SERVERLocal SOURCElocal-mcp

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/com-local-mcp-local-mcp/gdrive-root.md

WHAT IT DOES

What gdrive_root does on Local

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

RISK

Why gdrive_root is rated Low

The tool only lists/reads synced Google Drive folder paths available locally. It performs no writes, deletions, or executions — purely a directory enumeration operation with no side effects.

From the tool's definition Lists the Google Drive folders synced on this Mac... Reads the folder Google Drive for Desktop already syncs — no Google API, no OAuth.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gdrive_root safely

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

gdrive_root Allowed

gdrive_root 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": {
    "gdrive_root": {}
  }
}

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

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

FAQ

Questions about gdrive_root

What does the gdrive_root tool do? +

Lists the Google Drive folders synced on this Mac (My Drive, Shared drives, per-account mounts). Start here to get valid paths for the other gdrive_* tools. Reads the folder Google Drive for Desktop already syncs — no Google API, no OAuth. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gdrive_root? +

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

What risk level is gdrive_root? +

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

Can I rate-limit gdrive_root? +

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

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

gdrive_root is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

The MCP Attack Database →

Guides

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