drive_move_file · Google MCP: Risk & Policy

WHAT IT DOES

What drive_move_file does on Google

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

WHY IT NEEDS A POLICY

Why drive_move_file needs a policy

Moving a file changes its organizational structure and location metadata, which is a reversible modification. This is a Write operation rather than Destructive (the file is not deleted, just relocated) or Execute (no arbitrary code execution).

From the tool's definition Tool name is 'drive_move_file' and description states it 'Move a file to a different folder in Google Drive'. The action modifies the location/metadata of an existing file.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_move_file Rate-limited

drive_move_file 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": {
    "drive_move_file": {
      "limits": [
        {
          "counter": "drive_move_file_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, so you can run agents against it safely.

FAQ

Questions about drive_move_file

What does the drive_move_file tool do? +

Move a file to a different folder in Google Drive. It is categorised as a Write tool in the Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on drive_move_file? +

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

What risk level is drive_move_file? +

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

Can I rate-limit drive_move_file? +

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

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

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