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 definition in Dataverse, which is a reversible modification of the database schema. It does not delete data, execute arbitrary code, move money, or cause irreversible harm. The moderate severity reflects that adding columns can affect application behavior and data model integrity, but the change is typically reversible through column deletion.
From the tool's definition Tool name includes 'create' and description states 'Creates a new AutoNumber column in a Dataverse table', indicating creation of a new schema artifact. Requires 'solution context to be set first' showing it operates within managed solution boundaries.
Attacks that exploit this kind of access
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 (wizspdemo/dataverse-mcp3). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →