// MCP TOOL REFERENCE

delete_entity_key

ServerDataverse
CategoryDestructive

WHAT IT DOES

What delete_entity_key does on Dataverse

AI agents call delete_entity_key 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.

THE RISK

Critical Risk

Why delete_entity_key needs a policy

This tool permanently deletes a database key definition and its index, which is an irreversible action that cannot be restored without manual intervention. While the underlying data remains intact, the structural change to the database schema (removal of the unique index and key definition) is permanent and destructive. Clients relying on this key for upsert operations will break.

From the tool's definition "Permanently delete an alternate key", "Drops the supporting unique index", "cannot be undone" - the tool irreversibly removes a key definition and its supporting database index from the Dataverse table.

Documented attack patterns abuse exactly the kind of access delete_entity_key gives an agent:

POLICY

How to control delete_entity_key

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_entity_key:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_entity_key"
  ]
}

delete_entity_key disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Dataverse — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Dataverse tools

Destructive delete_attribute Permanently delete a column (attribute) from a Dataverse table. ⚠️ WARNING: this PERMANENT Destructive delete_picklist_option Remove an option from a Local or Global OptionSet (Dataverse DeleteOptionValue action). WA Destructive delete_record Delete a record from a Dataverse table Write add_attribute Add a column (attribute) to an existing Dataverse table Write add_entity_key Create an alternate key on a Dataverse table (composite supported via key_attributes). Use Write add_picklist_option Add an option to an existing Local or Global OptionSet (Dataverse InsertOptionValue action Write create_entity Create a new Dataverse table (entity) with specified attributes Write create_record Create a new record in a Dataverse table

All 22 Dataverse tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Dataverse → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_entity_key

What does the delete_entity_key tool do? +

Permanently delete an alternate key from a Dataverse table. ⚠️ Drops the supporting unique index; any client code relying on keyed-PATCH upserts against this key will stop working. The underlying attributes and their data are NOT affected — only the key definition and its index are removed. 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.

How do I enforce a policy on delete_entity_key? +

Register the Dataverse MCP server in PolicyLayer and add a rule for delete_entity_key: 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.

What risk level is delete_entity_key? +

delete_entity_key is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_entity_key? +

Yes. Add a rate_limit block to the delete_entity_key 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.

How do I block delete_entity_key completely? +

Set action: deny in the PolicyLayer policy for delete_entity_key. 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.

What MCP server provides delete_entity_key? +

delete_entity_key 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.

Enforce policy on every Dataverse tool call.

Start from Dataverse, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

22 Dataverse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.