insert_table
Inserts an empty rows x columns table at an index, or at the end of the body when index is omitted. Fill the cells afterwards: read_document_text shows the new table's range and per-cell layout, then insert_text into each cell (cell content ranges are visible in get_document; each cell holds its ...
This record as markdown: /tools/a1-x-tech-mcp-google-docs/insert-table.md
What insert_table does on Mcp Google Docs
AI agents use insert_table to create or update resources in Mcp Google Docs, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Docs environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
rows | integer | Yes | Number of rows. |
index | integer | — | Insertion index (from read_document_text). Omit to append at the end. |
tab_id | string | — | Tab to target (from list_tabs). Omit for the first/only tab. |
columns | integer | Yes | Number of columns (the API caps width). |
segment_id | string | — | Header/footer/footnote segment id (from get_document). Omit for the document body. |
document_id | string | Yes | The document id — the long id from the document URL (docs.google.com/document/d/<documentId>/edit) or from create_document output. |
Parameters from the server's own tool schema.
Why insert_table is rated Medium
An AI agent can call insert_table faster than any human can review: one bad instruction and it creates or modifies resources in Mcp Google Docs by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs insert_table safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For insert_table, this is the rule to start with:
insert_table 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 Mcp Google Docs, apply this rule, and every insert_table call is checked against it from then on.
Questions about insert_table
Inserts an empty rows x columns table at an index, or at the end of the body when index is omitted. Fill the cells afterwards: read_document_text shows the new table's range and per-cell layout, then insert_text into each cell (cell content ranges are visible in get_document; each cell holds its own paragraphs). Cell merging, cell background/borders and pinned header rows are not covered by typed tools — use raw_request with mergeTableCells/updateTableCellStyle/pinTableHeaderRows. It is categorised as a Write tool in the Mcp Google Docs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
insert_table accepts 6 parameters: rows, index, tab_id, columns, segment_id, document_id. Required: rows, columns, document_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Docs MCP server in PolicyLayer and add a rule for insert_table: 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 Docs. Nothing to install.
insert_table 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 insert_table 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 insert_table. 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.
insert_table is provided by the Mcp Google Docs MCP server (@a1-x-tech/mcp-google-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Docs, and thousands of servers like it.
This server
Across the catalogue