delete_column_from_table
Delete a column (0-based) from every row of a table.
This record as markdown: /tools/securityronin-docx-mcp/delete-column-from-table.md
What delete_column_from_table does on Docx
AI agents call delete_column_from_table to permanently remove resources in Docx, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_column_from_table is rated Critical
Deleting a column from a table is an irreversible operation that destroys data and structural elements within a document. Once executed, the column and all its contents are permanently removed without the ability to recover them through the tool itself (though document undo/versioning may apply at the application level).
From the tool's definition Tool name contains 'delete' and description states 'Delete a column...from every row of a table.' This operation irreversibly removes data structure and content from a Word document.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs delete_column_from_table safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_column_from_table, this is the rule to start with:
delete_column_from_table is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every delete_column_from_table call is checked against it from then on.
Questions about delete_column_from_table
Delete a column (0-based) from every row of a table. It is categorised as a Destructive tool in the Docx MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Docx MCP server in PolicyLayer and add a rule for delete_column_from_table: 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 Docx. Nothing to install.
delete_column_from_table 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_column_from_table 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_column_from_table. 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_column_from_table is provided by the Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docx, and thousands of servers like it.
Across the catalogue