update_dataverse_businessunit · Dataverse MCP Server MCP

WHAT IT DOES

What update_dataverse_businessunit does on Dataverse MCP Server

AI agents use update_dataverse_businessunit 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.

WHY IT NEEDS A POLICY

Why update_dataverse_businessunit needs a policy

This tool modifies organizational configuration in Dataverse (business unit properties, contact details, addresses, settings) but does not delete data or trigger destructive operations. The changes are reversible (properties can be re-updated). It is categorized as Write rather than Execute because it directly modifies data attributes rather than triggering arbitrary code execution.

From the tool's definition Tool name 'update_dataverse_businessunit' explicitly indicates modification of existing data. Description states 'Updates the properties and configuration of an existing business unit' and 'modify business unit information, contact details, addresses, and…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_dataverse_businessunit Rate-limited

update_dataverse_businessunit 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": {
    "update_dataverse_businessunit": {
      "limits": [
        {
          "counter": "update_dataverse_businessunit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dataverse MCP Server, so you can run agents against it safely.

FAQ

Questions about update_dataverse_businessunit

What does the update_dataverse_businessunit tool do? +

Updates the properties and configuration of an existing business unit. Use this to modify business unit information, contact details, addresses, and organizational settings. Only provided fields will be updated. 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 update_dataverse_businessunit? +

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

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

Can I rate-limit update_dataverse_businessunit? +

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

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

update_dataverse_businessunit is provided by the Dataverse MCP Server MCP server (wizspdemo/dataverse-mcp3). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.