update_dataverse_column

ServerDataverse MCP Server
CategoryWrite

How to control update_dataverse_column ↓

WHAT IT DOES

What update_dataverse_column does on Dataverse MCP Server

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

THE RISK

Medium Risk

Why update_dataverse_column needs a policy

Update operations that modify existing database schema are Write category. The severity is high because modifying column properties in an enterprise Dataverse environment could affect data validation rules, auditing, and application behavior across dependent systems.

From the tool's definition The tool description explicitly states it 'Updates the properties and configuration of an existing column in a Dataverse table' and allows modification of 'column settings like display names, descriptions, required levels, or audit settings.' This is a…

Documented attack patterns abuse exactly the kind of access update_dataverse_column gives an agent:

POLICY

How to control update_dataverse_column

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 update_dataverse_column:

policy.json

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

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

Create a free account and register Dataverse MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Dataverse MCP Server tools

Destructive convert_owner_team_to_access_team Converts an owner team to an access team, changing how the team can be used for record own Destructive delete_dataverse_businessunit Permanently deletes a business unit from Dataverse. WARNING: This action cannot be undone Destructive delete_dataverse_column Permanently deletes a column from a Dataverse table. WARNING: This action cannot be undone Destructive delete_dataverse_optionset Permanently deletes an option set from Dataverse. WARNING: This action cannot be undone an Destructive delete_dataverse_relationship Permanently deletes a relationship between Dataverse tables. WARNING: This action cannot b Destructive delete_dataverse_role Permanently deletes a security role from Dataverse. WARNING: This action cannot be undone Destructive delete_dataverse_table Permanently deletes a custom table from Dataverse. WARNING: This action cannot be undone a Destructive delete_dataverse_team Permanently deletes a team from Dataverse. WARNING: This action cannot be undone and will

All 71 Dataverse MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_dataverse_column

What does the update_dataverse_column tool do? +

Updates the properties and configuration of an existing column in a Dataverse table. Use this to modify column settings like display names, descriptions, required levels, or audit settings. Note that data type cannot be changed after creation. 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 update_dataverse_column? +

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

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

Can I rate-limit update_dataverse_column? +

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

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

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

Enforce policy on every Dataverse MCP Server tool call.

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.

CHECK YOUR STACK →

Free to start. No card required.

71 Dataverse MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.