drive_file_rename · Google Workspace MCP: Risk & Policy

WHAT IT DOES

What drive_file_rename does on Google Workspace

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

WHY IT NEEDS A POLICY

Why drive_file_rename needs a policy

Renaming a file modifies its metadata reversibly without deletion or destruction. This fits the Write category (creates or modifies data reversibly). Severity is medium because unintended renames could disrupt file organization and cause confusion or workflow disruption, but the action is easily undone by renaming again. Confidence is high based on the clear, unambiguous function name and description.

From the tool's definition Tool name 'drive_file_rename' and description 'Rename a file' indicate modification of file metadata in Google Drive. This is reversible (files can be renamed again) but alters existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_file_rename Rate-limited

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

FAQ

Questions about drive_file_rename

What does the drive_file_rename tool do? +

Rename a file. It is categorised as a Write tool in the Google Workspace 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_file_rename? +

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

What risk level is drive_file_rename? +

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

Can I rate-limit drive_file_rename? +

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

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

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