Delete specific rows from a Google Sheet
AI agents call delete_rows to permanently remove resources in Sheeter MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on spreadsheet data. Once rows are deleted, they cannot be automatically recovered without manual undo or backup restoration. The blast radius is high because an AI agent with access to this tool could accidentally or maliciously delete critical business data, rows containing important records, or entire datasets.
From the tool's definition Tool name 'delete_rows' and description 'Delete specific rows from a Google Sheet' explicitly indicate irreversible removal of data from a spreadsheet.
Attacks that exploit this kind of access
Delete specific rows from a Google Sheet. It is categorised as a Destructive tool in the Sheeter MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sheeter MCP Server MCP server in PolicyLayer and add a rule for delete_rows: 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 Sheeter MCP Server. Nothing to install.
delete_rows 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_rows 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_rows. 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_rows is provided by the Sheeter MCP Server MCP server (sarthaks97/sheeter-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 →