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.
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.
This tool performs a read-only operation that queries metadata about Dataverse table columns. It has no side effects, does not modify or delete data, does not execute code, and does not involve financial transactions. The filtering options mentioned are all query parameters that further constrain the read operation.
From the tool's definition The tool 'retrieves a list of columns' and is used to 'discover available fields' and 'get an overview of the table structure' - these are query and information-gathering operations with no data modification, deletion, or execution of code.
Attacks that exploit this kind of access
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.
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.
list_dataverse_columns is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
list_dataverse_columns is provided by the Dataverse MCP Server MCP server (wizspdemo/dataverse-mcp2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →