list_dataverse_columns

ServerDataverse MCP Server
CategoryRead

WHAT IT DOES

What list_dataverse_columns does on Dataverse MCP Server

AI agents call list_dataverse_columns to retrieve information from Dataverse MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why list_dataverse_columns needs a policy

This is a read-only query operation that retrieves schema metadata about table columns. It has no side effects—it does not create, modify, delete, or execute anything. The blast radius of misuse is minimal; an agent could only discover column names and metadata that may be sensitive in some contexts, but cannot act on that information to cause damage.

From the tool's definition Tool description states it 'Retrieves a list of columns in a specific Dataverse table' with 'filtering options' to 'discover available fields' and 'get an overview of the table structure'.

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

POLICY

How to control list_dataverse_columns

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_dataverse_columns": {}
  }
}

list_dataverse_columns is read-only, so it stays allowed — but 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.

CAP 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 →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_dataverse_columns

What does the list_dataverse_columns tool do? +

Retrieves a list of columns in a specific Dataverse table with filtering options. Use this to discover available fields in a table, find custom columns, or get an overview of the table structure. Supports filtering by custom/system columns and managed/unmanaged status. It is categorised as a Read tool in the Dataverse MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_dataverse_columns? +

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

list_dataverse_columns is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_dataverse_columns? +

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

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

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