Deletes multiple rows from a sheet
AI agents call bulk_delete_rows to permanently remove resources in Smartsheet 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 Smartsheet sheets without ability to undo. The 'bulk' qualifier amplifies the blast radius—a single misconfigured call could delete large volumes of data. While not financial, the irreversible nature and potential data loss impact place this in the Destructive category with high severity.
From the tool's definition Tool name 'bulk_delete_rows' and description 'Deletes multiple rows from a sheet' explicitly indicate irreversible deletion of data at scale.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Deletes multiple rows from a sheet. It is categorised as a Destructive tool in the Smartsheet MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Smartsheet MCP Server MCP server in PolicyLayer and add a rule for bulk_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 Smartsheet MCP Server. Nothing to install.
bulk_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 bulk_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 bulk_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.
bulk_delete_rows is provided by the Smartsheet MCP Server MCP server (thomaswtwrt/smar-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 →