Delete one or more rows by row number or unique_id lookup.
AI agents call delete_row to permanently remove resources in Google Connections — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes rows from spreadsheets without ability to undo (beyond Sheets' limited undo history). Deletion is irreversible at the API level and represents data loss. While not affecting financial systems directly or all users globally, accidental or malicious row deletion in a shared spreadsheet could destroy important records, affecting workflows and data integrity.
From the tool's definition Tool name 'delete_row' combined with description 'Delete one or more rows by row number or unique_id lookup' explicitly indicates irreversible deletion of data from Google Sheets.
Attacks that exploit this kind of access
Delete one or more rows by row number or unique_id lookup. It is categorised as a Destructive tool in the Google Connections MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Connections MCP server in PolicyLayer and add a rule for delete_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 Connections. Nothing to install.
delete_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_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_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_row is provided by the Google Connections MCP server (michaelzrork/google-connections-mcp). 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 →