New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

autoResizeRows

Auto-size one or more rows to fit their content. Indices are 0-based and the interval is half-open [startRow, endRow) — to auto-fit a single row at position 5, pass startRow: 5, endRow: 6.

SERVERGoogle Drive SOURCE@ark7/google-drive-mcp
Medium RISK CLASS
Category Write
Parameters 54 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ark7-google-drive-mcp/autoresizerows.md

What autoResizeRows does on Google Drive

AI agents use autoResizeRows 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.

ParameterTypeRequiredDescription
endRow number Yes 0-based end row index (exclusive); must be greater than startRow
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
sheetId number Yes Sheet ID (from getSpreadsheetInfo / listSheets). The default first sheet is usually 0.
startRow number Yes 0-based start row index (inclusive)
spreadsheetId string Yes Spreadsheet ID

Parameters from the server's own tool schema.

Why autoResizeRows is rated Medium

This tool creates or modifies data reversibly — it adjusts row heights but does not delete, destroy, execute arbitrary code, or move money. The operation can be undone (rows can be manually resized again), making it a Write action rather than Destructive. The blast radius is low since it only affects row formatting, not data integrity or critical operations.

From the tool's definition Tool modifies row dimensions in a Google Sheet by auto-sizing them to fit content. The description states it will 'auto-size one or more rows', which is a formatting modification operation that changes the spreadsheet structure reversibly.

Questions about autoResizeRows

What does the autoResizeRows tool do? +

Auto-size one or more rows to fit their content. Indices are 0-based and the interval is half-open [startRow, endRow) — to auto-fit a single row at position 5, pass startRow: 5, endRow: 6. 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.

What parameters does autoResizeRows accept? +

autoResizeRows accepts 5 parameters: endRow, account, sheetId, startRow, spreadsheetId. Required: endRow, sheetId, startRow, spreadsheetId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on autoResizeRows? +

Register the Google Drive MCP server in PolicyLayer and add a rule for autoResizeRows: 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.

What risk level is autoResizeRows? +

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

Can I rate-limit autoResizeRows? +

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

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

autoResizeRows 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Google Drive's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.