Delete a row from an existing table.
AI agents call gdoc_delete_table_row to permanently remove resources in Google Docs — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a table row is a destructive operation that cannot be automatically undone. While the action is scoped to a single table row (limiting blast radius compared to full document deletion), it permanently removes data. This is more severe than Write (which is reversible) but less critical than Financial operations.
From the tool's definition Tool name contains 'delete' and description states 'Delete a row from an existing table' — this irreversibly removes data from a document.
Attacks that exploit this kind of access
Delete a row from an existing table. It is categorised as a Destructive tool in the Google Docs MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Docs MCP server in PolicyLayer and add a rule for gdoc_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 Docs. Nothing to install.
gdoc_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 gdoc_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 gdoc_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.
gdoc_delete_table_row is provided by the Google Docs MCP server (node2flow-th/google-docs-mcp-community). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →