Delete column from a specific Retable
AI agents call delete_column to permanently remove resources in Retable MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a column from a table is an irreversible operation that destroys data and schema structure. This cannot be undone without backups. The tool permits permanent data loss affecting all rows in that column, making it Destructive rather than merely Write.
From the tool's definition Tool name is 'delete_column' and description states 'Delete column from a specific Retable'. The verb 'Delete' combined with the irreversible action of removing a column from a database/table structure clearly indicates destructive capability.
Attacks that exploit this kind of access
Delete column from a specific Retable. It is categorised as a Destructive tool in the Retable MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Retable MCP Server MCP server in PolicyLayer and add a rule for 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 Retable MCP Server. Nothing to install.
delete_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_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_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_column is provided by the Retable MCP Server MCP server (retable-io/mcp-server). 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 →