Creates a new global option set (choice list) in Dataverse with predefined options. Use this to create reusable choice lists that can be used across multiple tables and columns. Option sets provide consistent data entry options and improve data quality.
AI agents use create_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.
This tool creates new metadata objects (global option sets) in Dataverse, which is a reversible schema modification. It does not execute arbitrary code, delete data, move money, or destroy existing resources. The severity is medium because schema changes can affect applications and data validation across the platform, but the change is reversible (option sets can be modified or deleted).
From the tool's definition Tool description states it "Creates a new global option set (choice list) in Dataverse" - the verb "Creates" and action of adding new data structures to the schema indicate a write operation that modifies the Dataverse schema.
Documented attack patterns abuse exactly the kind of access create_dataverse_optionset gives an agent:
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 create_dataverse_optionset:
{
"version": "1",
"default": "deny",
"tools": {
"create_dataverse_optionset": {
"limits": [
{
"counter": "create_dataverse_optionset_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Free to start. No card required.
Creates a new global option set (choice list) in Dataverse with predefined options. Use this to create reusable choice lists that can be used across multiple tables and columns. Option sets provide consistent data entry options and improve data quality. 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.
Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_dataverse_optionset 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
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.