Delete a row from a table
AI agents call delete_table_row to permanently remove resources in LLM2Docs (Unofficial) — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes table row data from a Google Doc, which cannot be undone programmatically by an AI agent. While Google Docs has undo functionality, the tool itself performs an irreversible operation. The blast radius is high because an AI agent with unsupervised access could accidentally delete important structured data within documents.
From the tool's definition Tool name is 'delete_table_row' and description states 'Delete a row from a table'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a row from a table. It is categorised as a Destructive tool in the LLM2Docs (Unofficial) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LLM2Docs (Unofficial) 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 LLM2Docs (Unofficial). 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 LLM2Docs (Unofficial) MCP server (nomannayeem/google-docs-mcp-server). 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 →