# dataverse_delete_record

Delete a record from a Dataverse table

Agent View of the PolicyLayer registry record for `dataverse_delete_record`. HTML page: https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-delete-record

## Facts

- Tool: `dataverse_delete_record`
- Server: Dataverse MCP Server (`ajscheuer/dataverse-mcp`) — https://policylayer.com/tools/ajscheuer-dataverse-mcp.md
- Homepage: https://github.com/Ajscheuer/dataverse-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "dataverse_delete_record",
    "arguments": {}
  }
}
```

## 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 own definition: "Tool name 'dataverse_delete_record' and description 'Delete a record from a Dataverse table' explicitly perform irreversible deletion of data."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Dataverse MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "dataverse_delete_record"
  ]
}
```

## Other tools on Dataverse MCP Server (5)

- `dataverse_list_tables` — Read — https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-list-tables.md
- `dataverse_query_records` — Read — https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-query-records.md
- `dataverse_read_record` — Read — https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-read-record.md
- `dataverse_create_record` — Write — https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-create-record.md
- `dataverse_update_record` — Write — https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-update-record.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=ajscheuer-dataverse-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ajscheuer-dataverse-mcp