Converts an existing text column to an AutoNumber column by adding an AutoNumberFormat. The column must be a String type with Text format and should be empty or contain compatible data.
AI agents use convert_to_autonumber 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.
Converting a column type is a schema modification that changes the column definition and potentially transforms existing data. While reversible (the previous definition could theoretically be restored), this is a structural change to the database schema rather than a simple data creation/update. The requirement that 'The column must be...empty or contain compatible data' indicates potential data transformation.
From the tool's definition Tool description states it 'Converts an existing text column to an AutoNumber column by adding an AutoNumberFormat', which modifies the schema and data type of a column. This is a Write operation as it creates or modifies data structures reversibly.
Documented attack patterns abuse exactly the kind of access convert_to_autonumber 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 convert_to_autonumber:
{
"version": "1",
"default": "deny",
"tools": {
"convert_to_autonumber": {
"limits": [
{
"counter": "convert_to_autonumber_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}convert_to_autonumber 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.
Converts an existing text column to an AutoNumber column by adding an AutoNumberFormat. The column must be a String type with Text format and should be empty or contain compatible data. 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 convert_to_autonumber: 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.
convert_to_autonumber 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 convert_to_autonumber 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 convert_to_autonumber. 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.
convert_to_autonumber 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.