Add an option to an existing Local or Global OptionSet (Dataverse InsertOptionValue action). Requires Customizer or System Administrator role; HTTP 403 otherwise.
AI agents use add_picklist_option to create or update resources in Dataverse — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dataverse environment.
This tool creates new options in picklists/optionsets, which modifies data structure configuration reversibly. It is Write-category because the changes can be undone (options can be removed).
From the tool's definition Tool description states 'Add an option to an existing Local or Global OptionSet' and invokes 'InsertOptionValue action', indicating creation/modification of picklist options within Dataverse.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access add_picklist_option gives an agent:
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 add_picklist_option:
{
"version": "1",
"default": "deny",
"tools": {
"add_picklist_option": {
"limits": [
{
"counter": "add_picklist_option_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_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.
Free to start. No card required.
Add an option to an existing Local or Global OptionSet (Dataverse InsertOptionValue action). Requires Customizer or System Administrator role; HTTP 403 otherwise. 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.
Register the Dataverse MCP server in PolicyLayer and add a rule for add_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.
add_picklist_option is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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.
Set action: deny in the PolicyLayer policy for add_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.
add_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.
Start from Dataverse, 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.
22 Dataverse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.