manage_dimensions
Row/column operations on a run of rows (dimension=ROWS) or columns (dimension=COLUMNS), addressed by sheet_id + 0-based start_index (inclusive) and end_index (exclusive) — e.g. columns A-C = start 0, end 3. action=resize sets an exact pixel_size; auto_resize fits to content; insert adds empty row...
This record as markdown: /tools/a1-x-tech-mcp-google-sheets/manage-dimensions.md
What manage_dimensions does on Mcp Google Sheets
AI agents call manage_dimensions to permanently remove resources in Mcp Google Sheets, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | What to do with the rows/columns. |
sheet_id | integer | Yes | The numeric sheetId (NOT the title) from get_spreadsheet sheets[].properties.sheetId; the first sheet of a new spreadsheet is 0. |
dimension | string | Yes | Whether the run is rows or columns. |
end_index | integer | Yes | End of the run, exclusive (rows 1-3 = start 0, end 3). |
pixel_size | integer | — | resize: the new size in pixels. |
start_index | integer | Yes | First row/column of the run, 0-based inclusive. |
spreadsheet_id | string | Yes | The spreadsheet id — the long id from the URL (docs.google.com/spreadsheets/d/<spreadsheetId>/edit) or from create_spreadsheet / search_spreadsheets output. |
inherit_from_before | boolean | — | insert: new rows/columns copy formatting from before the insertion point (default: after). |
Parameters from the server's own tool schema.
Why manage_dimensions is rated Critical
Delete action irreversibly removes rows/columns and their data, shifting references permanently.
From the tool's definition delete removes them WITH their data (irreversible; cell references below/right shift)
Attacks that exploit this kind of access
The rule that runs manage_dimensions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Sheets, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For manage_dimensions, this is the rule to start with:
manage_dimensions 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 Mcp Google Sheets, apply this rule, and every manage_dimensions call is checked against it from then on.
Questions about manage_dimensions
Row/column operations on a run of rows (dimension=ROWS) or columns (dimension=COLUMNS), addressed by sheet_id + 0-based start_index (inclusive) and end_index (exclusive) — e.g. columns A-C = start 0, end 3. action=resize sets an exact pixel_size; auto_resize fits to content; insert adds empty rows/columns at start_index (inherit_from_before=true copies formatting from the row/column before instead of after); delete removes them WITH their data (irreversible; cell references below/right shift); hide/show toggle visibility without touching data; group/ungroup add or remove a collapsible outline group over the run (groups nest — repeat group on a subrange for a deeper level). It is categorised as a Destructive tool in the Mcp Google Sheets MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
manage_dimensions accepts 8 parameters: action, sheet_id, dimension, end_index, pixel_size, start_index, spreadsheet_id, inherit_from_before. Required: action, sheet_id, dimension, end_index, start_index, spreadsheet_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Sheets MCP server in PolicyLayer and add a rule for manage_dimensions: 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 Mcp Google Sheets. Nothing to install.
manage_dimensions 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 manage_dimensions 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 manage_dimensions. 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.
manage_dimensions is provided by the Mcp Google Sheets MCP server (@a1-x-tech/mcp-google-sheets). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Sheets, and thousands of servers like it.
Across the catalogue