Delete a column from an existing table.
AI agents call delete_table_column to permanently remove resources in Google Docs 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 a column and all its data from a table in a Google Doc. This operation cannot be undone through the tool itself (undo would depend on document revision history). While the blast radius is scoped to a single column rather than an entire document, the irreversible nature of deletion and data loss classifies this as Destructive rather than Write.
From the tool's definition Tool name is 'delete_table_column' and description states 'Delete a column from an existing table.' The verb 'delete' combined with the action of removing a column from a table represents irreversible data loss.
Attacks that exploit this kind of access
Delete a column from an existing table. It is categorised as a Destructive tool in the Google Docs MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Docs MCP Server MCP server in PolicyLayer and add a rule for delete_table_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 Google Docs MCP Server. Nothing to install.
delete_table_column 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_table_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.
Set action: deny in the PolicyLayer policy for delete_table_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.
delete_table_column is provided by the Google Docs MCP Server MCP server (nickweedon/google-docs-mcp-docker). 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 →