Permanently delete a column (attribute) from a Dataverse table. ⚠️ WARNING: this PERMANENTLY DESTROYS all data stored in this column across ALL records — there is no soft-delete, no undo, no recovery except from a full environment backup. Before calling this, make the user confirm explicitly and ...
AI agents call delete_attribute to permanently remove resources in Dataverse — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data at scale (all data in a column across all records) with no undo mechanism. The description explicitly warns of permanent destruction with recovery only through full backup restoration. This is the defining characteristic of Destructive category.
From the tool's definition Permanently delete a column (attribute) from a Dataverse table. ⚠️ WARNING: this PERMANENTLY DESTROYS all data stored in this column across ALL records — there is no soft-delete, no undo, no recovery except from a full environment backup.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access delete_attribute gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dataverse, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_attribute:
{
"version": "1",
"default": "deny",
"hide": [
"delete_attribute"
]
}delete_attribute 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.
Permanently delete a column (attribute) from a Dataverse table. ⚠️ WARNING: this PERMANENTLY DESTROYS all data stored in this column across ALL records — there is no soft-delete, no undo, no recovery except from a full environment backup. Before calling this, make the user confirm explicitly and consider: (1) is this a rename? then create the new column, migrate data, and only then delete the old one; (2) type change? same pattern. It is categorised as a Destructive tool in the Dataverse MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dataverse MCP server in PolicyLayer and add a rule for delete_attribute: 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. Nothing to install.
delete_attribute 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_attribute 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_attribute. 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_attribute is provided by the Dataverse MCP server (rededis/dataverse-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dataverse, 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.
22 Dataverse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.