# dataverse_read_record

Read a single record from a Dataverse table by ID

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

## Facts

- Tool: `dataverse_read_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: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why dataverse_read_record is rated Low

This tool retrieves data by querying a record using its ID. It performs no modifications, deletions, or external operations—purely a lookup/fetch operation. While the server supports destructive operations (dataverse_delete_record) and writes (dataverse_create_record, dataverse_update_record), this specific tool is limited to read-only retrieval.

From the tool's own definition: "Tool name is 'dataverse_read_record' and description states 'Read a single record from a Dataverse table by ID'. The verb 'Read' and action of retrieving a single record by identifier are characteristic of data retrieval with no side effects."

## Use case

AI agents call dataverse_read_record to retrieve information from Dataverse MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. 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_read_record": {}
  }
}
```

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