Delete multiple rows from a table at once using a list of row IDs
AI agents call delete_rows to permanently remove resources in Coda — 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 Coda table without the ability to undo via the tool itself. Deletion of multiple rows at once amplifies the blast radius—an AI agent with incorrect row IDs or flawed logic could destroy significant amounts of data. While not as critical as financial tools, the irreversible nature and potential for bulk data loss justifies 'high' severity and the Destructive category.
From the tool's definition Tool name 'delete_rows' and description 'Delete multiple rows from a table at once using a list of row IDs' explicitly indicate irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access delete_rows gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Coda, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_rows:
{
"version": "1",
"default": "deny",
"hide": [
"delete_rows"
]
}delete_rows disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete multiple rows from a table at once using a list of row IDs. It is categorised as a Destructive tool in the Coda MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Coda 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 Coda. 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 Coda MCP server (tjc-lp/coda-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Coda, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 Coda tools catalogued and risk-classified — across an index of 43,000+ MCP servers.