dataverse_delete_record

Delete a record from a Dataverse table

SERVERDataverse MCP Server SOURCEajscheuer/dataverse-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/ajscheuer-dataverse-mcp/dataverse-delete-record.md

What dataverse_delete_record does on Dataverse MCP Server

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

Why dataverse_delete_record is rated Critical

Deletion of database records cannot be undone and represents permanent data loss. This is the defining characteristic of the Destructive category. Severity is high rather than critical because the blast radius depends on which record is targeted, but unauthorized deletion of production data could cause significant business impact.

From the tool's definition Tool name 'dataverse_delete_record' and description 'Delete a record from a Dataverse table' explicitly perform irreversible deletion of data.

Questions about dataverse_delete_record

What does the dataverse_delete_record tool do? +

Delete a record from a Dataverse table. 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.

How do I enforce a policy on dataverse_delete_record? +

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

What risk level is dataverse_delete_record? +

dataverse_delete_record 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 dataverse_delete_record? +

Yes. Add a rate_limit block to the dataverse_delete_record 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 dataverse_delete_record completely? +

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

dataverse_delete_record is provided by the Dataverse MCP Server MCP server (ajscheuer/dataverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Dataverse MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Dataverse MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.