lockFile
Lock a file to prevent editing by setting content restrictions. The file remains readable but cannot be modified until unlocked.
This record as markdown: /tools/ark7-google-drive-mcp/lockfile.md
What lockFile does on Google Drive
AI agents use lockFile to create or update resources in Google Drive, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
fileId | string | Yes | ID of the file to lock |
reason | string | — | Reason for locking the file (shown to users who try to edit) |
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
ownerRestricted | boolean | — | If true, only the file owner can unlock the file (default: false) |
Parameters from the server's own tool schema.
Why lockFile is rated Medium
lockFile modifies file metadata (permissions/restrictions) reversibly—the locked state can be undone by unlocking. This is a Write operation that changes file properties. It is not Destructive because the action is reversible and does not delete or irreversibly overwrite data.
From the tool's definition Tool description states it 'prevent[s] editing by setting content restrictions' and 'cannot be modified until unlocked', indicating it modifies file access permissions and state rather than deleting data.
Attacks that exploit this kind of access
The rule that runs lockFile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lockFile, this is the rule to start with:
lockFile 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Drive, apply this rule, and every lockFile call is checked against it from then on.
Questions about lockFile
Lock a file to prevent editing by setting content restrictions. The file remains readable but cannot be modified until unlocked. It is categorised as a Write tool in the Google Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
lockFile accepts 4 parameters: fileId, reason, account, ownerRestricted. Required: fileId. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for lockFile: 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. Nothing to install.
lockFile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lockFile 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.
Set action: deny in the PolicyLayer policy for lockFile. 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.
lockFile is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
This server
Across the catalogue