drive_file_lock · Google Drive MCP Server MCP: Risk & Policy

WHAT IT DOES

What drive_file_lock does on Google Drive MCP Server

AI agents use drive_file_lock 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 drive_file_lock needs a policy

This tool modifies file metadata and access state (lock status) rather than deleting data or executing arbitrary code. It is reversible—files can be unlocked. It does not move money or execute external operations. The capability to lock/unlock files is a Write operation that changes collaborative properties of a document, which could interfere with other users' workflows if misused by an AI agent.

From the tool's definition The tool description states it can "Lock or unlock a file to prevent changes", indicating it modifies file access state and collaboration settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_file_lock Rate-limited

drive_file_lock 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_lock": {
      "limits": [
        {
          "counter": "drive_file_lock_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 drive_file_lock

What does the drive_file_lock tool do? +

Lock or unlock a file to prevent changes (Google Workspace only). 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 drive_file_lock? +

Register the Google Drive MCP Server MCP server in PolicyLayer and add a rule for drive_file_lock: 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 drive_file_lock? +

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

Can I rate-limit drive_file_lock? +

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

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

drive_file_lock is provided by the Google Drive MCP Server MCP server (rishipradeep-think41/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.