gdrive_move_files · Google Drive MCP Server MCP

WHAT IT DOES

What gdrive_move_files does on Google Drive MCP Server

AI agents use gdrive_move_files to create or update resources in Google Drive MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive MCP Server environment.

WHY IT NEEDS A POLICY

Why gdrive_move_files needs a policy

Moving files is a write operation because it modifies the organizational state of files (their location/parent folder) in a reversible manner. While the operation could impact file discoverability or access patterns, it does not delete data (thus not Destructive), execute code (thus not Execute), involve financial transactions (thus not Financial), or represent a read-only query (thus not Read).

From the tool's definition Tool description states 'Move one or more Google Drive files into a destination folder.' Moving files is a reversible modification operation that changes metadata (parent folder) without deleting or executing code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gdrive_move_files Rate-limited

gdrive_move_files stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gdrive_move_files": {
      "limits": [
        {
          "counter": "gdrive_move_files_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Drive MCP Server, so you can run agents against it safely.

FAQ

Questions about gdrive_move_files

What does the gdrive_move_files tool do? +

Move one or more Google Drive files into a destination folder. Use dryRun to preview changes. It is categorised as a Write tool in the Google Drive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gdrive_move_files? +

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

What risk level is gdrive_move_files? +

gdrive_move_files is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gdrive_move_files? +

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

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

gdrive_move_files is provided by the Google Drive MCP Server MCP server (konashevich/mcp-gdrive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.