This record as markdown: /tools/ark7-google-drive-mcp/mergegooglesheetcells.md
What mergeGoogleSheetCells does on Google Drive
AI agents use mergeGoogleSheetCells 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 |
|---|---|---|---|
range | string | Yes | Range to merge (e.g., 'A1:C3') |
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 |
mergeType | string | Yes | Merge type |
spreadsheetId | string | Yes | Spreadsheet ID |
Parameters from the server's own tool schema.
Why mergeGoogleSheetCells is rated Medium
Merging cells modifies the spreadsheet structure and formatting but does not delete or permanently destroy data—the merge operation can be undone. It is not a destructive operation (no irreversible deletion), not a read-only operation (it changes state), and not an execute/financial operation. It falls squarely into the Write category as a reversible modification.
From the tool's definition Tool name 'mergeGoogleSheetCells' and description 'Merge cells in a Google Sheet' indicate modification of spreadsheet formatting and structure. This is a reversible data transformation operation.
Attacks that exploit this kind of access
The rule that runs mergeGoogleSheetCells 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 mergeGoogleSheetCells, this is the rule to start with:
mergeGoogleSheetCells 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 mergeGoogleSheetCells call is checked against it from then on.
Questions about mergeGoogleSheetCells
Merge cells in a Google Sheet. 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.
mergeGoogleSheetCells accepts 4 parameters: range, account, mergeType, spreadsheetId. Required: range, mergeType, spreadsheetId. 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 mergeGoogleSheetCells: 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.
mergeGoogleSheetCells 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 mergeGoogleSheetCells 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 mergeGoogleSheetCells. 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.
mergeGoogleSheetCells 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