dataverse_query_records

Query multiple records from a Dataverse table with OData filters

SERVERDataverse MCP Server SOURCEajscheuer/dataverse-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/ajscheuer-dataverse-mcp/dataverse-query-records.md

WHAT IT DOES

What dataverse_query_records does on Dataverse MCP Server

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

RISK

Why dataverse_query_records is rated Low

This tool retrieves data from Dataverse tables using OData filtering. It has no side effects—it does not create, modify, delete, or execute external operations. While sensitive data exposure is a concern in any read operation, the capability itself is fundamentally a Read operation. Severity is low because misuse would result in unauthorized data disclosure rather than system compromise or destruction.

From the tool's definition Tool name 'dataverse_query_records' and description 'Query multiple records from a Dataverse table with OData filters' indicate a retrieval operation with no data modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dataverse_query_records safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Dataverse MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dataverse_query_records, this is the rule to start with:

dataverse_query_records Allowed

dataverse_query_records is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dataverse MCP Server, apply this rule, and every dataverse_query_records call is checked against it from then on.

FAQ

Questions about dataverse_query_records

What does the dataverse_query_records tool do? +

Query multiple records from a Dataverse table with OData filters. 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 dataverse_query_records? +

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

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

Can I rate-limit dataverse_query_records? +

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

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

dataverse_query_records is provided by the Dataverse MCP Server MCP server (ajscheuer/dataverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dataverse MCP Server, and thousands of servers like it.

This server

All 6 Dataverse MCP Server tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →