deleteRange
Delete content between start and end indices. Works on Google Docs and text/* files (e.g. text/plain, text/markdown). Index semantics differ by file type: Google Docs use the Docs API's 1-based structural position (includes structural elements); text files use 0-based Unicode code point (characte...
This record as markdown: /tools/ark7-google-drive-mcp/deleterange.md
What deleteRange does on Google Drive
AI agents call deleteRange to permanently remove resources in Google Drive, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
tabId | string | — | Optional. Google Docs only — Tab ID to delete from (from listDocumentTabs). If omitted, deletes from the first/default tab. Not supported on text files. |
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 |
endIndex | number | — | End index (exclusive). Google Docs: 1-based Docs API structural index. Text files: 0-based Unicode code point (character) offset. |
documentId | string | Yes | The Google Doc or text file ID |
startIndex | number | — | Start index (inclusive). Google Docs: 1-based Docs API structural index. Text files: 0-based Unicode code point (character) offset. Provide startIndex+endIndex |
textToFind | string | — | Google Docs only: delete the matched text instead of an index range (exact, case-sensitive match). Combine with matchInstance. A match that ends with the docume |
ifRevisionId | string | — | Optional optimistic lock: a revisionId from readGoogleDoc, getGoogleDocContent, getGoogleDocContentPaginated, or getDocumentInfo. The write fails cleanly if the |
matchInstance | number | — | Which instance of textToFind (default: 1) |
Parameters from the server's own tool schema.
Why deleteRange is rated Critical
An AI agent that decides to call deleteRange doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Google Drive is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs deleteRange 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 deleteRange, this is the rule to start with:
deleteRange is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Drive, apply this rule, and every deleteRange call is checked against it from then on.
Questions about deleteRange
Delete content between start and end indices. Works on Google Docs and text/* files (e.g. text/plain, text/markdown). Index semantics differ by file type: Google Docs use the Docs API's 1-based structural position (includes structural elements); text files use 0-based Unicode code point (character) offsets into the file content. For multi-tab Google Docs, specify tabId to target a specific tab — tabId is not supported on text files. It is categorised as a Destructive tool in the Google Drive MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteRange accepts 8 parameters: tabId, account, endIndex, documentId, startIndex, textToFind, ifRevisionId, matchInstance. Required: documentId. 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 deleteRange: 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.
deleteRange is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteRange 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 deleteRange. 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.
deleteRange 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.
Across the catalogue