List alternate keys defined on a Dataverse table. Returns a flat array of { logical_name, schema_name, display_name, key_attributes, entity_key_index_status, metadata_id }. entity_key_index_status reflects the background index build (Pending → Active, or Failed) — alt keys are not usable for keye...
AI agents call list_entity_keys 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 is a straightforward read operation that queries and retrieves metadata about alternate keys in a Dataverse table. It has no side effects, does not modify any data, and does not trigger any external operations. The information returned is metadata that helps understand table structure but does not itself perform any actions.
From the tool's definition The tool 'list_entity_keys' returns a flat array of entity key metadata (logical_name, schema_name, display_name, key_attributes, entity_key_index_status, metadata_id).
Documented attack patterns abuse exactly the kind of access list_entity_keys 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 list_entity_keys:
{
"version": "1",
"default": "deny",
"tools": {
"list_entity_keys": {}
}
}list_entity_keys 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.
List alternate keys defined on a Dataverse table. Returns a flat array of { logical_name, schema_name, display_name, key_attributes, entity_key_index_status, metadata_id }. entity_key_index_status reflects the background index build (Pending → Active, or Failed) — alt keys are not usable for keyed-PATCH upserts until Active. 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 list_entity_keys: 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.
list_entity_keys 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_entity_keys 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_entity_keys. 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_entity_keys 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.