Permanently deletes a column from a Dataverse table. WARNING: This action cannot be undone and will remove all data stored in this column. Use with extreme caution and only for columns that are no longer needed.
AI agents call delete_dataverse_column to permanently remove resources in Dataverse MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes schema objects and associated data with no undo capability. The explicit warnings about permanence and data loss, combined with the blast radius of losing an entire column's data across potentially thousands of records in a production Dataverse environment, place this in the Destructive category at critical severity.
From the tool's definition Tool name explicitly states 'delete' and description states: 'Permanently deletes a column from a Dataverse table. WARNING: This action cannot be undone and will remove all data stored in this column.' The warnings emphasize irreversibility and data loss.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Permanently deletes a column from a Dataverse table. WARNING: This action cannot be undone and will remove all data stored in this column. Use with extreme caution and only for columns that are no longer needed. It is categorised as a Destructive tool in the Dataverse MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for delete_dataverse_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 Dataverse MCP Server. Nothing to install.
delete_dataverse_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_dataverse_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_dataverse_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_dataverse_column is provided by the Dataverse MCP Server MCP server (wizspdemo/dataverse-mcp2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
delete_dataverse_column is one line of Dataverse MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →