create_dataverse_column · Dataverse MCP Server MCP

WHAT IT DOES

What create_dataverse_column does on Dataverse MCP Server

AI agents use create_dataverse_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.

WHY IT NEEDS A POLICY

Why create_dataverse_column needs a policy

This tool creates new database schema elements (columns/fields) in Dataverse tables. Schema modifications are reversible through deletion, making this a Write operation rather than Destructive. The severity is medium because adding columns can impact existing applications and data handling, but the effect is confined to schema structure rather than data loss.

From the tool's definition Tool description states it 'Creates a new column (field) in a Dataverse table' with 'specified data type and configuration' and 'add new fields to store specific data in your tables'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_dataverse_column Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_dataverse_column": {
      "limits": [
        {
          "counter": "create_dataverse_column_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 create_dataverse_column

What does the create_dataverse_column tool do? +

Creates a new column (field) in a Dataverse table with the specified data type and configuration. Supports various column types including text, numbers, dates, lookups, and choice lists. Use this to add new fields to store specific data in your tables. 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.

How do I enforce a policy on create_dataverse_column? +

Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for create_dataverse_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.

What risk level is create_dataverse_column? +

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

Can I rate-limit create_dataverse_column? +

Yes. Add a rate_limit block to the create_dataverse_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.

How do I block create_dataverse_column completely? +

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

What MCP server provides create_dataverse_column? +

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