update_picklist_option

THE RISK

Medium Risk

Why update_picklist_option needs a policy

This tool modifies existing picklist options in Dataverse, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely read data (Read). The severity is medium because incorrect updates to picklist options could disrupt business logic or user workflows, but the change can be reverted by updating again.

From the tool's definition Tool name 'update_picklist_option' and description 'Update an existing option' indicate modification of data. Picklist options are configuration elements in Dataverse that define dropdown values. The verb 'update' performs a reversible modification.

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

POLICY

How to control update_picklist_option

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

policy.json

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

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

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

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Dataverse tools

Destructive delete_attribute Permanently delete a column (attribute) from a Dataverse table. ⚠️ WARNING: this PERMANENT Destructive delete_entity_key Permanently delete an alternate key from a Dataverse table. ⚠️ Drops the supporting unique Destructive delete_picklist_option Remove an option from a Local or Global OptionSet (Dataverse DeleteOptionValue action). WA Destructive delete_record Delete a record from a Dataverse table Write add_attribute Add a column (attribute) to an existing Dataverse table Write add_entity_key Create an alternate key on a Dataverse table (composite supported via key_attributes). Use Write add_picklist_option Add an option to an existing Local or Global OptionSet (Dataverse InsertOptionValue action Write create_entity Create a new Dataverse table (entity) with specified attributes

All 22 Dataverse tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_picklist_option

What does the update_picklist_option tool do? +

Update an existing option. It is categorised as a Write tool in the Dataverse 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_picklist_option? +

Register the Dataverse MCP server in PolicyLayer and add a rule for update_picklist_option: 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. Nothing to install.

What risk level is update_picklist_option? +

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

Can I rate-limit update_picklist_option? +

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

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

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

Enforce policy on every Dataverse tool call.

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

CHECK YOUR STACK →