convert_to_autonumber · Dataverse MCP Server MCP

WHAT IT DOES

What convert_to_autonumber does on Dataverse MCP Server

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.

WHY IT NEEDS A POLICY

Why convert_to_autonumber needs a policy

This tool modifies existing database schema by converting a column's type and format. While not destructive (the change is technically reversible by converting back), it qualifies as Write because it irreversibly alters column properties and could break existing code/integrations that depend on the column's current format.

From the tool's definition Converts an existing text column to an AutoNumber column by adding an AutoNumberFormat. This modifies the column structure and schema in Dataverse, which is a persistent schema change operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

convert_to_autonumber Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "convert_to_autonumber": {
      "limits": [
        {
          "counter": "convert_to_autonumber_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dataverse MCP Server, so you can run agents against it safely.

FAQ

Questions about convert_to_autonumber

What does the convert_to_autonumber tool do? +

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.

How do I enforce a policy on convert_to_autonumber? +

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.

What risk level is convert_to_autonumber? +

convert_to_autonumber is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit convert_to_autonumber? +

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.

How do I block convert_to_autonumber completely? +

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.

What MCP server provides convert_to_autonumber? +

convert_to_autonumber 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.