insertTable
Insert a new table with the specified dimensions at a given index. For multi-tab docs, specify tabId to target a specific tab.
This record as markdown: /tools/ark7-google-drive-mcp/inserttable.md
What insertTable does on Google Drive
AI agents use insertTable 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 |
|---|---|---|---|
rows | number | Yes | Number of rows for the new table |
index | number | Yes | The index (1-based) where the table should be inserted |
tabId | string | — | Optional. Tab ID to insert the table into (from listDocumentTabs). If omitted, inserts into the first/default tab. |
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 |
columns | number | Yes | Number of columns for the new table |
documentId | string | Yes | The document ID |
ifRevisionId | string | — | Optional optimistic lock: a revisionId from readGoogleDoc, getGoogleDocContent, getGoogleDocContentPaginated, or getDocumentInfo. The write fails cleanly if the |
Parameters from the server's own tool schema.
Why insertTable is rated Medium
This tool creates/modifies document content (a table insertion) without deleting data or executing arbitrary code. It is clearly Write-category because the change is reversible.
From the tool's definition The tool description explicitly states it will 'Insert a new table' into a Google Document. Insertion of new content is a reversible Write operation—the table can be deleted or modified afterward.
Attacks that exploit this kind of access
The rule that runs insertTable 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 insertTable, this is the rule to start with:
insertTable 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 insertTable call is checked against it from then on.
Questions about insertTable
Insert a new table with the specified dimensions at a given index. For multi-tab docs, specify tabId to target a specific tab. 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.
insertTable accepts 7 parameters: rows, index, tabId, account, columns, documentId, ifRevisionId. Required: rows, index, columns, 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 insertTable: 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.
insertTable 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 insertTable 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 insertTable. 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.
insertTable 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