set_autonumber_seed · Dataverse MCP Server MCP

WHAT IT DOES

What set_autonumber_seed does on Dataverse MCP Server

AI agents use set_autonumber_seed 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 set_autonumber_seed needs a policy

This tool creates or modifies AutoNumber column configuration (the seed value), which is a Write operation. It does not execute arbitrary code, delete data, or move money. However, the blast radius is medium because altering AutoNumber seeds could cause duplicate-key conflicts, business logic failures, or data integrity issues if the new seed overlaps with existing numbers in production systems.

From the tool's definition Sets the seed value for an AutoNumber column — this modifies a column's configuration without deleting it, making it a reversible data change operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_autonumber_seed Rate-limited

set_autonumber_seed 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": {
    "set_autonumber_seed": {
      "limits": [
        {
          "counter": "set_autonumber_seed_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 set_autonumber_seed

What does the set_autonumber_seed tool do? +

Sets the seed value for an AutoNumber column\. 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 set_autonumber_seed? +

Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for set_autonumber_seed: 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 set_autonumber_seed? +

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

Can I rate-limit set_autonumber_seed? +

Yes. Add a rate_limit block to the set_autonumber_seed 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 set_autonumber_seed completely? +

Set action: deny in the PolicyLayer policy for set_autonumber_seed. 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 set_autonumber_seed? +

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