GOOGLESUPER_DELETE_TABLE_ROW
Tool to delete a row from a table in a Google Document. Use when you need to remove a specific row from an existing table.
This record as markdown: /tools/googlesuper/googlesuper-delete-table-row.md
What GOOGLESUPER_DELETE_TABLE_ROW does on Google Super
AI agents call GOOGLESUPER_DELETE_TABLE_ROW to permanently remove resources in Google Super, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
documentId | string | — | The ID of the document. |
tableCellLocation | object | — | The reference table cell location from which the row will be deleted. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_DELETE_TABLE_ROW is rated Critical
Deleting a row from a Google Document table cannot be undone by the tool itself and permanently removes data. While the user could theoretically undo via Google Docs history, the tool's action is destructive in nature. This ranks higher than Write (which is reversible) and reaches Destructive category.
From the tool's definition Tool name contains 'DELETE' and description states 'delete a row from a table' — this is irreversible data removal.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_DELETE_TABLE_ROW safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_DELETE_TABLE_ROW, this is the rule to start with:
GOOGLESUPER_DELETE_TABLE_ROW 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 Google Super, apply this rule, and every GOOGLESUPER_DELETE_TABLE_ROW call is checked against it from then on.
Questions about GOOGLESUPER_DELETE_TABLE_ROW
Tool to delete a row from a table in a Google Document. Use when you need to remove a specific row from an existing table. It is categorised as a Destructive tool in the Google Super MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
GOOGLESUPER_DELETE_TABLE_ROW accepts 2 parameters: documentId, tableCellLocation. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_DELETE_TABLE_ROW: 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 Super. Nothing to install.
GOOGLESUPER_DELETE_TABLE_ROW 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 GOOGLESUPER_DELETE_TABLE_ROW 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 GOOGLESUPER_DELETE_TABLE_ROW. 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.
GOOGLESUPER_DELETE_TABLE_ROW is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
Across the catalogue