delete_table_row
Delete rows from a table in a google docs document.
This record as markdown: /tools/dev-ithitchhiker-mcp-google-docs/delete-table-row.md
What delete_table_row does on Mcp Google Docs
AI agents call delete_table_row to permanently remove resources in Mcp Google Docs, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_table_row is rated Critical
Deletion operations that cannot be undone fall into the Destructive category. While Google Docs maintains version history allowing recovery, the tool's primary action is irreversible data removal at the document level. An AI agent misusing this could permanently lose table rows from user documents.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete rows from a table in a google docs document.' The operation irreversibly removes data from a Google Docs table.
Attacks that exploit this kind of access
The rule that runs delete_table_row 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 delete_table_row, this is the rule to start with:
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 Mcp Google Docs, apply this rule, and every delete_table_row call is checked against it from then on.
Questions about delete_table_row
Delete rows from a table in a google docs document. It is categorised as a Destructive tool in the Mcp Google Docs MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Google Docs MCP server in PolicyLayer and add a rule for 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 Mcp Google Docs. Nothing to install.
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 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 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.
delete_table_row is provided by the Mcp Google Docs MCP server (dev-ithitchhiker/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.
Across the catalogue