AI agents call numbers_delete_row to permanently remove resources in Iwork — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of spreadsheet rows is a destructive operation that cannot be undone programmatically by the tool itself. While the user could undo via Cmd+Z in the UI, an AI agent calling this tool has permanently removed data from the active document. This represents a high blast radius if invoked unintentionally or on the wrong table/rows, making it Destructive rather than Write.
From the tool's definition Tool name 'numbers_delete_row' and description 'Delete one or more rows from a table' explicitly indicate irreversible deletion of data from a Numbers spreadsheet.
Documented attack patterns abuse exactly the kind of access numbers_delete_row gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Iwork, and nothing reaches the server without passing your rules. This is the rule we recommend for numbers_delete_row:
{
"version": "1",
"default": "deny",
"hide": [
"numbers_delete_row"
]
}numbers_delete_row 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 one or more rows from a table. It is categorised as a Destructive tool in the Iwork MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Iwork MCP server in PolicyLayer and add a rule for numbers_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 Iwork. Nothing to install.
numbers_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 numbers_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 numbers_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.
numbers_delete_row is provided by the Iwork MCP server (reichenbach/iwork_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Iwork, 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.
114 Iwork tools catalogued and risk-classified — across an index of 43,000+ MCP servers.