Medium Risk

update_dataverse_optionset

Updates an existing option set by modifying its properties and managing its options. Use this to add new choices, update existing ones, remove obsolete options, or change the option set

How to control update_dataverse_optionset ↓

What update_dataverse_optionset does on Dataverse MCP Server

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

Medium Risk

Why update_dataverse_optionset needs a policy

This tool creates or modifies option set configurations within Dataverse—a core data schema management operation. It is Write rather than Destructive because option set changes are typically reversible (options can be re-added, renamed, or restored through version history/solutions in enterprise Dataverse environments).

From the tool's definition The tool "updates an existing option set by modifying its properties and managing its options" including to "add new choices, update existing ones, remove obsolete options." These are reversible modifications to data structure and configuration.

Documented attack patterns abuse exactly the kind of access update_dataverse_optionset gives an agent:

How to control update_dataverse_optionset

PolicyLayer is an MCP gateway — it sits between your AI agents and Dataverse MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_dataverse_optionset:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_dataverse_optionset": {
      "limits": [
        {
          "counter": "update_dataverse_optionset_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Dataverse MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about update_dataverse_optionset

What does the update_dataverse_optionset tool do? +

Updates an existing option set by modifying its properties and managing its options. Use this to add new choices, update existing ones, remove obsolete options, or change the option set. 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_optionset? +

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

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

Can I rate-limit update_dataverse_optionset? +

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

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

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

Enforce policy on every Dataverse MCP Server tool call.

Start from Dataverse MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

71 Dataverse MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.