Creates a new AutoNumber column in a Dataverse table with specified format. AutoNumber columns automatically generate alphanumeric strings using sequential numbers, random strings, and datetime placeholders. Requires a solution context to be set first.
AI agents use create_autonumber_column 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 a new column in a Dataverse table, which is a reversible write operation that modifies the schema. It does not execute arbitrary code, delete data, or move money. The severity is medium because schema changes can have downstream effects on dependent objects and applications, but the operation is reversible (the column can be deleted).
From the tool's definition Tool description states it 'Creates a new AutoNumber column in a Dataverse table' and 'automatically generate alphanumeric strings'. The word 'Creates' indicates data structure modification.
Documented attack patterns abuse exactly the kind of access create_autonumber_column 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_autonumber_column:
{
"version": "1",
"default": "deny",
"tools": {
"create_autonumber_column": {
"limits": [
{
"counter": "create_autonumber_column_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_autonumber_column 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 AutoNumber column in a Dataverse table with specified format. AutoNumber columns automatically generate alphanumeric strings using sequential numbers, random strings, and datetime placeholders. Requires a solution context to be set first. 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_autonumber_column: 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_autonumber_column 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_autonumber_column 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_autonumber_column. 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_autonumber_column 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.