Critical Risk →

numbers_delete_column

Delete one or more columns from a table

How to control numbers_delete_column ↓

What numbers_delete_column does on Iwork

AI agents call numbers_delete_column 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.

Critical Risk

Why numbers_delete_column needs a policy

The tool performs an irreversible operation that removes data columns from a Numbers spreadsheet. Deletion cannot be undone programmatically by the tool itself, making this a Destructive action. The severity is high because an AI agent could accidentally or maliciously delete critical spreadsheet columns containing important data.

From the tool's definition Tool name 'numbers_delete_column' combined with description 'Delete one or more columns from a table' explicitly indicates irreversible deletion of spreadsheet data.

Documented attack patterns abuse exactly the kind of access numbers_delete_column gives an agent:

How to control numbers_delete_column

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_column:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "numbers_delete_column"
  ]
}

numbers_delete_column disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Iwork — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about numbers_delete_column

What does the numbers_delete_column tool do? +

Delete one or more columns 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.

How do I enforce a policy on numbers_delete_column? +

Register the Iwork MCP server in PolicyLayer and add a rule for numbers_delete_column: 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.

What risk level is numbers_delete_column? +

numbers_delete_column is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit numbers_delete_column? +

Yes. Add a rate_limit block to the numbers_delete_column 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.

How do I block numbers_delete_column completely? +

Set action: deny in the PolicyLayer policy for numbers_delete_column. 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.

What MCP server provides numbers_delete_column? +

numbers_delete_column 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.

Enforce policy on every Iwork tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.