list_entities

THE RISK

Low Risk

Why list_entities needs a policy

This tool retrieves or queries information about entities in Dataverse without creating, modifying, or deleting data. It has no side effects beyond returning metadata. Optional filters (prefix and solution) are query parameters that constrain the read operation. The blast radius of misuse is minimal—an agent could enumerate entities but cannot alter or damage data.

From the tool's definition Tool name is 'list_entities' and description states 'List Dataverse tables (entities)' — a retrieval operation with no modification.

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

POLICY

How to control list_entities

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

policy.json

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

list_entities 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 — 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 tools

Destructive delete_attribute Permanently delete a column (attribute) from a Dataverse table. ⚠️ WARNING: this PERMANENT Destructive delete_entity_key Permanently delete an alternate key from a Dataverse table. ⚠️ Drops the supporting unique Destructive delete_picklist_option Remove an option from a Local or Global OptionSet (Dataverse DeleteOptionValue action). WA Destructive delete_record Delete a record from a Dataverse table Write add_attribute Add a column (attribute) to an existing Dataverse table Write add_entity_key Create an alternate key on a Dataverse table (composite supported via key_attributes). Use Write add_picklist_option Add an option to an existing Local or Global OptionSet (Dataverse InsertOptionValue action Write create_entity Create a new Dataverse table (entity) with specified attributes

All 22 Dataverse 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_entities

What does the list_entities tool do? +

List Dataverse tables (entities) with optional prefix and solution filters. It is categorised as a Read tool in the Dataverse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_entities? +

Register the Dataverse MCP server in PolicyLayer and add a rule for list_entities: 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.

What risk level is list_entities? +

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

Can I rate-limit list_entities? +

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

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

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

Enforce policy on every Dataverse tool call.

Start from Dataverse, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →