# dataverse_create_record

Create a new record in a Dataverse table

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

## Facts

- Tool: `dataverse_create_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_create_record",
    "arguments": {}
  }
}
```

## Why dataverse_create_record is rated Medium

This tool creates new records in Dataverse, which is reversible data modification (Write category). Severity is medium because creating records could introduce invalid data, cause business logic issues, or consume storage, but the impact is typically correctable through deletion.

From the tool's own definition: "Tool name 'dataverse_create_record' and description 'Create a new record in a Dataverse table' indicate data creation/modification without deletion."

## Use case

AI agents use dataverse_create_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_create_record": {
      "limits": [
        {
          "counter": "dataverse_create_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_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