Query records from a Dataverse table with OData filters
AI agents call query_records to retrieve information from Dataverse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from a Dataverse table using OData filtering. It performs no side effects—no data is created, modified, or deleted. It is a straightforward read operation with minimal risk. The low severity reflects that unauthorized queries expose data but do not corrupt or destroy it.
From the tool's definition Tool name 'query_records' and description 'Query records from a Dataverse table with OData filters' indicate data retrieval without modification. The verb 'Query' and 'OData filters' are standard read-only operations.
Documented attack patterns abuse exactly the kind of access query_records gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dataverse, and nothing reaches the server without passing your rules. This is the rule we recommend for query_records:
{
"version": "1",
"default": "deny",
"tools": {
"query_records": {}
}
}query_records is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query records from a Dataverse table with OData filters. It is categorised as a Read tool in the Dataverse MCP Server, which means it retrieves data without modifying state.
Register the Dataverse MCP server in PolicyLayer and add a rule for 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. Nothing to install.
query_records 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 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.
Set action: deny in the PolicyLayer policy for 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.
query_records is provided by the Dataverse MCP server (rededis/dataverse-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dataverse, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 Dataverse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.