Delete a row from an existing table.
AI agents call delete_table_row to permanently remove resources in Google Docs MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data from a Google Docs table without possibility of reversal (except through Google Docs version history, but the operation itself cannot be undone programmatically). Although the blast radius is constrained to a single table row rather than an entire document, the irreversible nature of deletion classifies it as Destructive rather than Write.
From the tool's definition Tool name is 'delete_table_row' with description 'Delete a row from an existing table.' The verb 'delete' and action of removing table data is irreversible and fits the Destructive definition of 'irreversibly deletes or overwrites data.'
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 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Docs MCP Server 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 Google Docs MCP Server. 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 Google Docs MCP Server MCP server (nickweedon/google-docs-mcp-docker). 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 →