# dataverse_update_record

Update an existing record in a Dataverse table

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

## Facts

- Tool: `dataverse_update_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: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why dataverse_update_record is rated Medium

The tool modifies existing data reversibly (updates rather than deletes), which places it in the Write category. Severity is medium rather than high because updates are reversible and do not permanently destroy data. This is less severe than Destructive actions but more impactful than Read operations. Confidence is high based on clear language in both name and description.

From the tool's own definition: "Tool name 'dataverse_update_record' and description 'Update an existing record in a Dataverse table' indicate modification of data."

## Use case

AI agents use dataverse_update_record to create or update resources in Dataverse MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dataverse MCP Server environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "dataverse_update_record": {
      "limits": [
        {
          "counter": "dataverse_update_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Dataverse MCP Server (5)

- `dataverse_delete_record` — Destructive — https://policylayer.com/tools/ajscheuer-dataverse-mcp/dataverse-delete-record.md
- `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

## 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