edit_table

SERVERMcp Google Docs SOURCE@a1-x-tech/mcp-google-docs

Medium RISK CLASS

Category Write

Parameters 83 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/a1-x-tech-mcp-google-docs/edit-table.md

WHAT IT DOES

What edit_table does on Mcp Google Docs

AI agents use edit_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
`action`	string	Yes	What to do with the table.
`tab_id`	string	—	Tab to target (from list_tabs). Omit for the first/only tab.
`row_index`	integer	—	0-based row of the anchor cell (default 0).
`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.
`column_index`	integer	—	0-based column of the anchor cell (default 0).
`insert_below`	boolean	—	insert_row only: insert below the anchor row (default true; false = above).
`insert_right`	boolean	—	insert_column only: insert right of the anchor column (default true; false = left).
`table_start_index`	integer	Yes	The table's start index (the table block's start in read_document_text).

Parameters from the server's own tool schema.

RISK

Why edit_table is rated Medium

An AI agent can call edit_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.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs edit_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 edit_table, this is the rule to start with:

edit_table Rate-limited

edit_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "edit_table": {
      "limits": [
        {
          "counter": "edit_table_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Docs, apply this rule, and every edit_table call is checked against it from then on.

FAQ

Questions about edit_table

What does the edit_table tool do? +

Inserts or deletes a row/column of an existing table. The table is addressed by table_start_index — the table block's start index from read_document_text (its startIndex in get_document). action=insert_row adds next to the cell at row_index/column_index (insert_below, default true); insert_column likewise (insert_right, default true); delete_row / delete_column remove the row/column containing that cell WITH ALL ITS CONTENT — that content is unrecoverable. row_index/column_index are 0-based and default to 0. Deleting shifts every later index in the document; re-read before further edits. 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.

What parameters does edit_table accept? +

edit_table accepts 8 parameters: action, tab_id, row_index, document_id, column_index, insert_below, insert_right, table_start_index. Required: action, document_id, table_start_index. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on edit_table? +

Register the Mcp Google Docs MCP server in PolicyLayer and add a rule for edit_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.

What risk level is edit_table? +

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

Can I rate-limit edit_table? +

Yes. Add a rate_limit block to the edit_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.

How do I block edit_table completely? +

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

What MCP server provides edit_table? +

edit_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.

KEEP EXPLORING

More on Mcp Google Docs, and thousands of servers like it.

This server

All 27 Mcp Google Docs tools →

Across the catalogue

edit_screen on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →