dataverse_update_record

Update an existing record in a Dataverse table

SERVERDataverse MCP Server SOURCEajscheuer/dataverse-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

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

WHAT IT DOES

What dataverse_update_record does on Dataverse MCP Server

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.

RISK

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 definition Tool name 'dataverse_update_record' and description 'Update an existing record in a Dataverse table' indicate modification of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dataverse_update_record safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Dataverse MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dataverse_update_record, this is the rule to start with:

dataverse_update_record Rate-limited

dataverse_update_record stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dataverse MCP Server, apply this rule, and every dataverse_update_record call is checked against it from then on.

FAQ

Questions about dataverse_update_record

What does the dataverse_update_record tool do? +

Update an existing record in a Dataverse table. It is categorised as a Write tool in the Dataverse MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dataverse_update_record? +

Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for dataverse_update_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_update_record? +

dataverse_update_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dataverse_update_record? +

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

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

dataverse_update_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.

KEEP EXPLORING

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

This server

All 6 Dataverse MCP Server tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →