AI agents call excel_delete_columns to permanently remove resources in Excel — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting columns is an irreversible operation that permanently removes data and cannot be undone programmatically. Even if the file is not saved immediately, the action constitutes a destructive modification. In the context of game configuration files (per server description), deleting columns could corrupt game balance data, remove critical metadata, or break cross-sheet references.
From the tool's definition Tool name 'excel_delete_columns' combined with description '删除列' (Chinese for 'delete columns') indicates irreversible deletion of data columns from Excel files. Sibling tools include 'excel_delete_rows', confirming this server's destructive capabilities.
Documented attack patterns abuse exactly the kind of access excel_delete_columns gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Excel, and nothing reaches the server without passing your rules. This is the rule we recommend for excel_delete_columns:
{
"version": "1",
"default": "deny",
"hide": [
"excel_delete_columns"
]
}excel_delete_columns 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.
删除列. It is categorised as a Destructive tool in the Excel MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Excel MCP server in PolicyLayer and add a rule for excel_delete_columns: 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 Excel. Nothing to install.
excel_delete_columns 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 excel_delete_columns 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 excel_delete_columns. 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.
excel_delete_columns is provided by the Excel MCP server (tangentdomain/excel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Excel, 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.
36 Excel tools catalogued and risk-classified — across an index of 43,000+ MCP servers.